[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e846622b-2a3b-45cd-9ccb-7b92583f47f9@ideasonboard.com>
Date: Tue, 10 Dec 2024 10:01:09 +0200
From: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Luca Ceresoli <luca.ceresoli@...tlin.com>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, Wolfram Sang <wsa@...nel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Cosmin Tanislav <demonsingur@...il.com>,
Tomi Valkeinen <tomi.valkeinen+renesas@...asonboard.com>,
stable@...r.kernel.org
Subject: Re: [PATCH v2 1/3] i2c: atr: Fix client detach
Hi,
On 22/11/2024 16:07, Andy Shevchenko wrote:
> On Fri, Nov 22, 2024 at 02:26:18PM +0200, Tomi Valkeinen wrote:
>> From: Tomi Valkeinen <tomi.valkeinen+renesas@...asonboard.com>
>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen+renesas@...asonboard.com>
>
> We (used to?) have a check in Linux Next against missing SoB of the committer,
> wouldn't this trap into it?
I don't think linux-next can check that. Or rather, it can, but the
committer there (which is the subsystem maintainer, probably) is not
related to the sender of this mail, so I don't think linux-next can
complain about this particular issue.
I didn't right away figure out how to easily change the From address for
the email with the standard tooling. As this is such a clear case of the
sender and the author being the same person, I'll just ignore this point
for now (although strictly speaking I think you're right).
Tomi
Powered by blists - more mailing lists