[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6231246b-f8a5-4a6b-a7b2-dc2815ffa85b@linux.microsoft.com>
Date: Tue, 7 Nov 2023 14:28:40 -0800
From: Vijay Balakrishna <vijayb@...ux.microsoft.com>
To: Wolfram Sang <wsa@...nel.org>, roman.bacik@...adcom.com,
andi.shyti@...nel.org, rjui@...adcom.com, sbranden@...adcom.com,
bcm-kernel-feedback-list@...adcom.com, linux-i2c@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i2c: iproc: handle invalid slave state
On 8/28/2023 12:10 PM, Wolfram Sang wrote:
> On Thu, Aug 24, 2023 at 02:23:51PM -0700, roman.bacik@...adcom.com wrote:
>> From: Roman Bacik <roman.bacik@...adcom.com>
>>
>> Add the code to handle an invalid state when both bits S_RX_EVENT
>> (indicating a transaction) and S_START_BUSY (indicating the end
>> of transaction - transition of START_BUSY from 1 to 0) are set in
>> the interrupt status register during a slave read.
>>
>> Signed-off-by: Roman Bacik <roman.bacik@...adcom.com>
>> Fixes: 1ca1b4516088 ("i2c: iproc: handle Master aborted error")
>
> Applied to for-next, thanks!
>
Hi Wolfram,
I don't see this patch neither in I2C for-next nor in linux-next. May
be got lost by accident, please update.
Thanks,
Vijay
Powered by blists - more mailing lists