From: Mikko Perttunen <cyndis@kapsi.fi>
To: Wolfram Sang <wsa@kernel.org>, Mikko Perttunen <mperttunen@nvidia.com>
Cc: thierry.reding@gmail.com, jonathanh@nvidia.com, talho@nvidia.com,
linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] i2c: bpmp-tegra: Ignore unknown I2C_M flags
Date: Mon, 18 Jan 2021 13:22:16 +0200 [thread overview]
Message-ID: <99326ffc-7590-84ce-dfa7-7c09bc17ca31@kapsi.fi> (raw)
In-Reply-To: <20210117112003.GB1983@ninjato>
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@vger.kernel.org # v4.19+
>> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.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
next prev parent reply other threads:[~2021-01-18 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 10:22 [PATCH v3] i2c: bpmp-tegra: Ignore unknown I2C_M flags Mikko Perttunen
2021-01-17 11:20 ` Wolfram Sang
2021-01-18 11:22 ` Mikko Perttunen [this message]
2021-01-18 11:34 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99326ffc-7590-84ce-dfa7-7c09bc17ca31@kapsi.fi \
--to=cyndis@kapsi.fi \
--cc=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=talho@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=wsa@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox