From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH AUTOSEL 5.5 495/542] docs: i2c: writing-clients: properly name the stop condition Date: Sun, 16 Feb 2020 19:06:30 -0500 Message-ID: <20200217000630.GK1734@sasha-vm> References: <20200214154854.6746-1-sashal@kernel.org> <20200214154854.6746-495-sashal@kernel.org> <20200215071402.027c9120@endymion> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Return-path: Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org To: Luca Ceresoli Cc: Jean Delvare , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Wolfram Sang , linux-i2c@vger.kernel.org List-Id: linux-i2c@vger.kernel.org On Sun, Feb 16, 2020 at 10:49:39PM +0100, Luca Ceresoli wrote: >Hi, > >On 15/02/20 07:14, Jean Delvare wrote: >> On Fri, 14 Feb 2020 10:48:07 -0500, Sasha Levin wrote: >>> From: Luca Ceresoli >>> >>> [ Upstream commit 4fcb445ec688a62da9c864ab05a4bd39b0307cdc ] >>> >>> In I2C there is no such thing as a "stop bit". Use the proper naming: "stop >>> condition". >>> >>> Signed-off-by: Luca Ceresoli >>> Reported-by: Jean Delvare >>> Reviewed-by: Jean Delvare >>> Signed-off-by: Wolfram Sang >>> Signed-off-by: Sasha Levin >>> --- >>> Documentation/i2c/writing-clients.rst | 6 +++--- >>> 1 file changed, 3 insertions(+), 3 deletions(-) >>> >>> diff --git a/Documentation/i2c/writing-clients.rst b/Documentation/i2c/writing-clients.rst >>> index ced309b5e0cc8..3869efdf84cae 100644 >>> --- a/Documentation/i2c/writing-clients.rst >>> +++ b/Documentation/i2c/writing-clients.rst >>> @@ -357,9 +357,9 @@ read/written. >>> >>> This sends a series of messages. Each message can be a read or write, >>> and they can be mixed in any way. The transactions are combined: no >>> -stop bit is sent between transaction. The i2c_msg structure contains >>> -for each message the client address, the number of bytes of the message >>> -and the message data itself. >>> +stop condition is issued between transaction. The i2c_msg structure >>> +contains for each message the client address, the number of bytes of the >>> +message and the message data itself. >>> >>> You can read the file ``i2c-protocol`` for more information about the >>> actual I2C protocol. >> >> I wouldn't bother backporting this documentation patch to stable and >> longterm trees. That's a minor vocabulary thing really, it does not >> qualify. > >I also feel no need to have it in stable branches. Hovever it would not >hurt, so whatever is fine for who's maintaining that branch will be fine >for me as well. No, you're right, this isn't stable material - I've missed it during review and I'll drop it now. Thanks for pointing it out. -- Thanks, Sasha