From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Linus Walleij <linus.walleij@linaro.org>,
Roel Kluin <roel.kluin@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] unset twsi option3 for gconfig as well
Date: Mon, 14 Oct 2013 21:09:14 +0200 [thread overview]
Message-ID: <525C415A.2020505@gmail.com> (raw)
In-Reply-To: <20131014190247.GN5402@titan.lakedaemon.net>
On 10/14/2013 09:02 PM, Jason Cooper wrote:
> On Mon, Oct 14, 2013 at 08:43:49PM +0200, Sebastian Hesselbarth wrote:
> ...
>> You know a good way to determine how far it should go back to -stable?
>
> $ git blame -L 338,338 drivers/pinctrl/mvebu/pinctrl-dove.c
> c9f95ced drivers/pinctrl/pinctrl-dove.c (Sebastian Hesselbarth
> 2012-09-13 17:41:44 +0200 338) gcfg2 &= ~(DOVE_TWSI_ENABLE_OPTION2 |
> DOVE_TWSI_ENABLE_OPTION2);
>
> $ git tag --contains c9f95ced | grep '^v[23]\.[0-9][0-9]*' | sed -r -e
> 's/^(v[23]\.[0-9][0-9]*).*$/\1.x/' | sort -uV
> v3.7.x
> v3.8.x
> v3.9.x
> v3.10.x
> v3.11.x
> v3.12.x
>
> so it should get flagged for v3.7 and newer.
>
> Watch out for really old stuff, the regex above doesn't properly handle
> v2.6.XX.x...
Ok, it is not in pre-v3.0, so the regex is fine. Thanks for the above -
and I also see git magic to resolve the rename of pinctrl-dove.c :)
If it originates from before the rename, I guess we need two different
-stable patches, one for pre-rename, one for post-rename?
Sebastian
next prev parent reply other threads:[~2013-10-14 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 23:27 [PATCH] unset twsi option3 for gconfig as well Roel Kluin
2013-10-14 7:08 ` Linus Walleij
2013-10-14 7:12 ` Thomas Petazzoni
2013-10-14 18:43 ` Sebastian Hesselbarth
2013-10-14 19:02 ` Jason Cooper
2013-10-14 19:09 ` Sebastian Hesselbarth [this message]
2013-10-14 19:15 ` Jason Cooper
2013-10-15 7:39 ` Thomas Petazzoni
2013-10-16 11:35 ` 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=525C415A.2020505@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=thomas.petazzoni@free-electrons.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).