[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99326ffc-7590-84ce-dfa7-7c09bc17ca31@kapsi.fi>
Date: Mon, 18 Jan 2021 13:22:16 +0200
From: Mikko Perttunen <cyndis@...si.fi>
To: Wolfram Sang <wsa@...nel.org>,
Mikko Perttunen <mperttunen@...dia.com>
Cc: thierry.reding@...il.com, jonathanh@...dia.com, talho@...dia.com,
linux-i2c@...r.kernel.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v3] i2c: bpmp-tegra: Ignore unknown I2C_M flags
On 1/17/21 1:20 PM, Wolfram Sang wrote:
> On Tue, Jan 12, 2021 at 12:22:25PM +0200, Mikko Perttunen wrote:
>> In order to not to start returning errors when new I2C_M flags are
>> added, change behavior to just ignore all flags that we don't know
>> about. This includes the I2C_M_DMA_SAFE flag that already exists.
>>
>> Cc: stable@...r.kernel.org # v4.19+
>> Signed-off-by: Mikko Perttunen <mperttunen@...dia.com>
>
> Applied to for-current, thanks! I added also this sentence from v2 to
> the description to justify stable: "but causes -EINVAL to be returned
> for valid transactions."
Thanks!
>
> Also, this driver has no dedicated maintainer. Is there someone up for
> this task? There is probably little to do and it will speed up patch
> acceptance because I pick patches once the driver maintainer is happy.
>
I think it falls under the 'TEGRA ARCHITECTURE SUPPORT' wildcard
(Thierry and Jon). Do we need a more specific maintainer entry?
If it's helpful to Thierry and Jon, I guess I could pick it up.
Mikko
Powered by blists - more mailing lists