devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Jason Cooper <jason@lakedaemon.net>
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: Wed, 12 Mar 2014 15:02:02 +0100	[thread overview]
Message-ID: <CACRpkdbcbMNim9LRkr75Mk5yHfwbA1OAexByHG50qDUPwts4uQ@mail.gmail.com> (raw)
In-Reply-To: <20140307134616.GR1872@titan.lakedaemon.net>

On Fri, Mar 7, 2014 at 2:46 PM, Jason Cooper <jason@lakedaemon.net> wrote:
> On Fri, Mar 07, 2014 at 11:56:11AM +0800, Linus Walleij wrote:

>> 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).

I've applied this patch [3/3] to the pinctrl tree.

> 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.

No, I mean, please apply patch 1/3 and 2/3 to the mvebu tree.
There is no need to sync DTS and pinctrl driver changes. This
patch to the pinctrl driver I want to carry however.

Yours,
Linus Walleij

  reply	other threads:[~2014-03-12 14:02 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
     [not found]   ` <1393977790-29110-2-git-send-email-sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-06 20:15     ` Jason Cooper
     [not found] ` <1393977790-29110-1-git-send-email-sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
     [not found]     ` <1393977790-29110-4-git-send-email-sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
     [not found]               ` <CACRpkdbEQSj7jLWT2BFR22m7phwmyKCByhQuFFgHvHoKvQFD5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-07 13:46                 ` Jason Cooper
2014-03-12 14:02                   ` Linus Walleij [this message]
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=CACRpkdbcbMNim9LRkr75Mk5yHfwbA1OAexByHG50qDUPwts4uQ@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --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;
as well as URLs for NNTP newsgroup(s).