From: Jason Cooper <jason@lakedaemon.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@arm.linux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Gregory Clement <gregory.clement@free-electrons.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] pinctrl: mvebu: silence WARN to dev_warn
Date: Fri, 7 Mar 2014 08:46:16 -0500 [thread overview]
Message-ID: <20140307134616.GR1872@titan.lakedaemon.net> (raw)
In-Reply-To: <CACRpkdbEQSj7jLWT2BFR22m7phwmyKCByhQuFFgHvHoKvQFD5g@mail.gmail.com>
On Fri, Mar 07, 2014 at 11:56:11AM +0800, Linus Walleij wrote:
> On Fri, Mar 7, 2014 at 11:50 AM, Jason Cooper <jason@lakedaemon.net> wrote:
> > On Fri, Mar 07, 2014 at 11:48:25AM +0800, Linus Walleij wrote:
> >> On Fri, Mar 7, 2014 at 4:18 AM, Jason Cooper <jason@lakedaemon.net> wrote:
> >> > On Wed, Mar 05, 2014 at 01:03:10AM +0100, Sebastian Hesselbarth wrote:
> >> >> Pinctrl will WARN on missing DT resources, which is a little bit too
> >> >> noisy. Use dev_warn with FW_BUG instead.
> >> >>
> >> >> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> >> >> ---
> >> >> Cc: Russell King <linux@arm.linux.org.uk>
> >> >> Cc: Jason Cooper <jason@lakedaemon.net>
> >> >> Cc: Andrew Lunn <andrew@lunn.ch>
> >> >> Cc: Gregory Clement <gregory.clement@free-electrons.com>
> >> >> Cc: Linus Walleij <linus.walleij@linaro.org>
> >> >> Cc: devicetree@vger.kernel.org
> >> >> Cc: linux-arm-kernel@lists.infradead.org
> >> >> Cc: linux-kernel@vger.kernel.org
> >> >> ---
> >> >> drivers/pinctrl/mvebu/pinctrl-dove.c | 3 ++-
> >> >> 1 file changed, 2 insertions(+), 1 deletion(-)
> >> >
> >> > Applied to mvebu/pinctrl
> >>
> >> So are you carrying this patch, or shall I apply it to my tree?
> >>
> >> In the former case: Acked-by: Linus Walleij <linus.walleij@linaro.org>
> >
> > I'll send you a pull tomorrow.
>
> For a single patch?
Well, just the doc change and WARN change. I've already taken the dts
change into mvebu/dt (for arm-soc).
There should be no need for these two to be in mvebu's for-next, so if
it's easier for you to pick them, please do so.
I'll drop them from mvebu/pinctrl and update mvebu's for-next right now.
thx,
Jason.
next prev parent reply other threads:[~2014-03-07 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 0:03 [PATCH 0/3] pinctrl: mvebu: prepare for single PMU node Sebastian Hesselbarth
2014-03-05 0:03 ` [PATCH 1/3] ARM: dove: drop pinctrl PMU reg property Sebastian Hesselbarth
2014-03-06 20:15 ` Jason Cooper
2014-03-05 0:03 ` [PATCH 2/3] devicetree: bindings: " Sebastian Hesselbarth
2014-03-06 20:17 ` Jason Cooper
2014-03-05 0:03 ` [PATCH 3/3] pinctrl: mvebu: silence WARN to dev_warn Sebastian Hesselbarth
2014-03-06 20:18 ` Jason Cooper
2014-03-07 3:48 ` Linus Walleij
2014-03-07 3:50 ` Jason Cooper
2014-03-07 3:56 ` Linus Walleij
2014-03-07 13:46 ` Jason Cooper [this message]
2014-03-12 14:02 ` Linus Walleij
2014-03-12 15:46 ` Jason Cooper
2014-03-05 9:12 ` [PATCH 0/3] pinctrl: mvebu: prepare for single PMU node Andrew Lunn
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=20140307134616.GR1872@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sebastian.hesselbarth@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
all inboxes | Powered by JetHome®