From nobody Thu Feb 12 21:45:56 2026 Received: from mail.zeus03.de (www.zeus03.de [194.117.254.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F0EEF196C7D for ; Fri, 7 Jun 2024 11:17:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717759059; cv=none; b=lN5XnzuGEO71rY5jU2O1jDjeZTlV2ILmFKXW9GkYK8q1dwhBvSIw/ntJ4dRgiAwv4yK39ntfkR1+jcAax8llpJBSUF2J0jWNGVY8BKk3FtT+4IJyTRDC7JLHDcXHvr7HE/OZon0vQoitY7Dkr+HG3Y8DO7ajmem7fuD0eqS6O4g= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717759059; c=relaxed/simple; bh=IP1Nz8/r7nBHvBlG1CYD83Zy5oYQuFGfgfVEWKA6gGU=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=Z+kIpdOJo3UD7p36tafplZontpO2xr+lqWLEL3wYjaLesR8ORsWG19+72b2ej+mNlfrNbKDuIXoST52/dTWuB0YqFj/1UiOEUz6ZsV6QzjheO17qV/rIgG9PWDt/5Ny52iRqkB4C0I3LiVZpPhTPiB0m+8oD2+2kl185ZDt0EMk= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=Yz4YcP8x; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="Yz4YcP8x" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=k1; bh=qeFGc1MhuDAIZaUAFfDVzSOlEu6 39tUIn02dg463xvM=; b=Yz4YcP8xTHRV7hbFpkIF2ayX8iVhH453QknxZiwe+Hl z17XQGYqH/iOYQOv7lnE7HTDWtkKdGojhL4FHl6+9ULRqE9+oxp0n7wHFPcKEXmV +wbW5vsfmoro7GxYRR/oeJiL2Z8xLiR7Upb1c6uf7WEbvaumeIGCoGpa8ZN21KWD H8ftDjaYRhNPRRO+mQk39B1G6KZVHeC2g74l/IpDBoug9BDVeXjDdkJB7bRj3Nxo uhSbB7an/sFnlmEoA/kcAR6rNjk1rzi9wubN1EvzJWlPtwZBThs8nmKSVd7dHCgW DZdS8R6j8lxRLW/M+cERcE9xL4+rOer3NfZSKVZnraw== Received: (qmail 3292160 invoked from network); 7 Jun 2024 13:17:33 +0200 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 7 Jun 2024 13:17:33 +0200 X-UD-Smtp-Session: l3s3148p1@mxko8koaDLAgAwDPXzLGAH1eNELjOc3g From: Wolfram Sang To: linux-i2c@vger.kernel.org Cc: Easwar Hariharan , Andi Shyti , linux-doc@vger.kernel.org, Wolfram Sang , linux-kernel@vger.kernel.org Subject: [PATCH 1/5] docs: i2c: summary: start sentences consistently. Date: Fri, 7 Jun 2024 13:17:20 +0200 Message-ID: <20240607111726.12678-2-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240607111726.12678-1-wsa+renesas@sang-engineering.com> References: <20240607111726.12678-1-wsa+renesas@sang-engineering.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Change the first paragraphs to contain only one space after the end of the previous sentence like in the rest of the document. Signed-off-by: Wolfram Sang Reviewed-by: Easwar Hariharan --- Documentation/i2c/summary.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/i2c/summary.rst b/Documentation/i2c/summary.rst index 786c618ba3be..28ff80a2302b 100644 --- a/Documentation/i2c/summary.rst +++ b/Documentation/i2c/summary.rst @@ -4,10 +4,10 @@ Introduction to I2C and SMBus =20 I=C2=B2C (pronounce: I squared C and written I2C in the kernel documentati= on) is a protocol developed by Philips. It is a slow two-wire protocol (variable -speed, up to 400 kHz), with a high speed extension (3.4 MHz). It provides +speed, up to 400 kHz), with a high speed extension (3.4 MHz). It provides an inexpensive bus for connecting many types of devices with infrequent or -low bandwidth communications needs. I2C is widely used with embedded -systems. Some systems use variants that don't meet branding requirements, +low bandwidth communications needs. I2C is widely used with embedded +systems. Some systems use variants that don't meet branding requirements, and so are not advertised as being I2C but come under different names, e.g. TWI (Two Wire Interface), IIC. =20 @@ -18,14 +18,14 @@ access the PDF. An older version of the specification (= revision 6) is archived `here `_. =20 SMBus (System Management Bus) is based on the I2C protocol, and is mostly -a subset of I2C protocols and signaling. Many I2C devices will work on an +a subset of I2C protocols and signaling. Many I2C devices will work on an SMBus, but some SMBus protocols add semantics beyond what is required to -achieve I2C branding. Modern PC mainboards rely on SMBus. The most common +achieve I2C branding. Modern PC mainboards rely on SMBus. The most common devices connected through SMBus are RAM modules configured using I2C EEPRO= Ms, and hardware monitoring chips. =20 Because the SMBus is mostly a subset of the generalized I2C bus, we can -use its protocols on many I2C systems. However, there are systems that do= n't +use its protocols on many I2C systems. However, there are systems that don= 't meet both SMBus and I2C electrical constraints; and others which can't implement all the common SMBus protocol semantics or messages. =20 --=20 2.43.0