From: Linus Walleij <linus.walleij@linaro.org>
To: Fabio Estevam <festevam@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-stable@vger.kernel.org
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Sascha Hauer <kernel@pengutronix.de>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Subject: Re: [PATCH] gpio: generic: clamp values from bgpio_get_set()
Date: Tue, 15 Dec 2015 09:37:53 +0100 [thread overview]
Message-ID: <CACRpkdZoz8vM1Jiyn7y39d14ezO4F5PLGXT2S5F8CKbWjAZrAw@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5D22UWVOr3J-LgwB41w8XJcvyraeKgfvgUpCr1Uv8kL6A@mail.gmail.com>
On Fri, Dec 11, 2015 at 11:23 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Fri, Dec 11, 2015 at 8:10 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
>
>>>> Fixes: b19e7f51a55f "gpio: gpio-generic: add flag to read out output value from reg_set"
>>>
>>> This commit appeared in 4.2, so it would be nice to add a stable tag:
>>>
>>> Cc: <stable@vger.kernel.org> # 4.2+
>>
>> IIUC Fixes: has exactly this effect: it will be applied to any kernel where
>> that commit is present. The beauty of git commit hashes.
>
> Not sure if this has the same effect as it is not mentioned at
> Documentation/stable_kernel_rules.txt
I have surely noticed it having that effect in practice, maybe it is time
to send a patch to that document.
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-12-15 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 21:36 [PATCH] gpio: generic: clamp values from bgpio_get_set() Linus Walleij
2015-12-11 21:47 ` Fabio Estevam
2015-12-11 22:10 ` Linus Walleij
2015-12-11 22:23 ` Fabio Estevam
2015-12-15 8:37 ` Linus Walleij [this message]
2015-12-15 17:00 ` Greg KH
2015-12-17 8:22 ` Linus Walleij
2015-12-17 13:49 ` Vladimir Zapolskiy
2015-12-17 14:49 ` Linus Walleij
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=CACRpkdZoz8vM1Jiyn7y39d14ezO4F5PLGXT2S5F8CKbWjAZrAw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=acourbot@nvidia.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-stable@vger.kernel.org \
--cc=vladimir_zapolskiy@mentor.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).