From: Wolfram Sang <wsa@kernel.org>
To: 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: Sun, 17 Jan 2021 12:20:03 +0100 [thread overview]
Message-ID: <20210117112003.GB1983@ninjato> (raw)
In-Reply-To: <20210112102225.3737326-1-mperttunen@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
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."
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-17 11:20 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 [this message]
2021-01-18 11:22 ` Mikko Perttunen
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=20210117112003.GB1983@ninjato \
--to=wsa@kernel.org \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).