[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c3ss6ralf4tpyknsda5p745a65xjprlzecdq3s4zy4dpckuxi4@izf7emrzykay>
Date: Thu, 24 Oct 2024 15:22:56 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Tommy Huang <tommy_huang@...eedtech.com>
Cc: Andrew Jeffery <andrew@...econstruct.com.au>,
"brendanhiggins@...gle.com" <brendanhiggins@...gle.com>, "benh@...nel.crashing.org" <benh@...nel.crashing.org>,
"joel@....id.au" <joel@....id.au>, BMC-SW <BMC-SW@...eedtech.com>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>, "openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "stable@...r.kernel.org" <stable@...r.kernel.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] i2c: aspeed: Consider i2c reset for muti-master case
Hi Tommy,
On Tue, Oct 22, 2024 at 02:42:08AM +0000, Tommy Huang wrote:
> Hi Andrew,
>
> Thanks for your comments.
> I want to fix the situation when our controller is set as target mode and reading / writing by other i2c host.
> However, this host is stopped by any other reason (DC on/off..etc).
> It will cause the controller is stuck in this situation.
> But I find it might not have clear hints to identify this situation is normal or abnormal.
> So, this patch should not be applied into mainstream.
Please, avoid top posting, I don't understand which part of the
original message you are trying to comment on.
Second thing, please, before sending a patch, always always
always make sure that checkpatch.pl reports '0' errors and '0'
warnings, except for few sporadic cases.
Andi
Powered by blists - more mailing lists