From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Keerthy <j-keerthy@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tero Kristo <t-kristo@ti.com>, Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH v2] pinctrl: pinctrl-single: Fix pcs_parse_bits_in_pinctrl_entry to use __ffs than ffs
Date: Tue, 26 Apr 2016 09:17:04 -0700 [thread overview]
Message-ID: <20160426161704.GU5995@atomide.com> (raw)
In-Reply-To: <CACRpkdZa=v1iKZ=eiY11V3qZV9pPqtoi6vHm2Pu4ctWTFiy0TA@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [160423 02:46]:
> On Fri, Apr 15, 2016 at 5:22 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Linus Walleij <linus.walleij@linaro.org> [160415 02:29]:
> >> Patch applied for fixes with Tony's ACK.
> >>
> >> Should it also be tagged for stable?
> >
> > Probably a good idea, I can see somebody pulling hair out because
> > of this in various product trees.
>
> Ooops sorry I totally missed to add that :(
>
> Please ask Greg to take it as a selected stable patch.
Well it has the fixes tag, let's see if the stable people will
find it automatically now :) If not, Keerthy can send email
requesting adding it manually to stable trees.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] pinctrl: pinctrl-single: Fix pcs_parse_bits_in_pinctrl_entry to use __ffs than ffs
Date: Tue, 26 Apr 2016 09:17:04 -0700 [thread overview]
Message-ID: <20160426161704.GU5995@atomide.com> (raw)
In-Reply-To: <CACRpkdZa=v1iKZ=eiY11V3qZV9pPqtoi6vHm2Pu4ctWTFiy0TA@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [160423 02:46]:
> On Fri, Apr 15, 2016 at 5:22 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Linus Walleij <linus.walleij@linaro.org> [160415 02:29]:
> >> Patch applied for fixes with Tony's ACK.
> >>
> >> Should it also be tagged for stable?
> >
> > Probably a good idea, I can see somebody pulling hair out because
> > of this in various product trees.
>
> Ooops sorry I totally missed to add that :(
>
> Please ask Greg to take it as a selected stable patch.
Well it has the fixes tag, let's see if the stable people will
find it automatically now :) If not, Keerthy can send email
requesting adding it manually to stable trees.
Tony
next prev parent reply other threads:[~2016-04-26 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 4:59 [PATCH v2] pinctrl: pinctrl-single: Fix pcs_parse_bits_in_pinctrl_entry to use __ffs than ffs Keerthy
2016-04-14 4:59 ` Keerthy
2016-04-14 4:59 ` Keerthy
2016-04-14 16:02 ` Tony Lindgren
2016-04-14 16:02 ` Tony Lindgren
2016-04-15 9:27 ` Linus Walleij
2016-04-15 9:27 ` Linus Walleij
2016-04-15 15:22 ` Tony Lindgren
2016-04-15 15:22 ` Tony Lindgren
2016-04-23 9:45 ` Linus Walleij
2016-04-23 9:45 ` Linus Walleij
2016-04-26 16:17 ` Tony Lindgren [this message]
2016-04-26 16:17 ` Tony Lindgren
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=20160426161704.GU5995@atomide.com \
--to=tony@atomide.com \
--cc=j-keerthy@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.