From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 REPOST 5/5] pinctrl: tegra: Add complete device tree support
Date: Tue, 10 Apr 2012 20:31:23 +0200 [thread overview]
Message-ID: <CACRpkdb=8ydKuX52cen8Y_iBzV+RwD61NCPrjQFXNgoO-=bc9Q@mail.gmail.com> (raw)
In-Reply-To: <4F8457F9.7090309@wwwdotorg.org>
On Tue, Apr 10, 2012 at 5:55 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
> Is your pinctrl for-next branch considered "stable" (i.e. it won't ever
> be rebased) at least up to commit a57be23 "pinctrl: tegra: Add complete
> device tree support"?
Not quite yet, because I would expect the occasional -rc fix for
-rc3 or so.
> If so, I'll use it as a base for the Tegra GPIO and pinmux rework branch.
Soon-ish that'd work...
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-04-10 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 15:27 [PATCH V4 REPOST 1/5] dt: add property iteration helpers Stephen Warren
2012-04-04 15:27 ` [PATCH V4 REPOST 2/5] dt: pinctrl: Document device tree binding Stephen Warren
2012-04-10 8:18 ` Linus Walleij
2012-04-04 15:27 ` [PATCH V4 REPOST 3/5] dt: Move Tegra20 pin mux binding into new pinctrl directory Stephen Warren
2012-04-10 8:20 ` Linus Walleij
2012-04-04 15:27 ` [PATCH V4 REPOST 4/5] dt: Document Tegra20/30 pinctrl binding Stephen Warren
2012-04-10 8:23 ` Linus Walleij
2012-04-04 15:27 ` [PATCH V4 REPOST 5/5] pinctrl: tegra: Add complete device tree support Stephen Warren
2012-04-10 8:25 ` Linus Walleij
2012-04-10 15:55 ` Stephen Warren
2012-04-10 18:31 ` Linus Walleij [this message]
2012-04-10 19:02 ` Stephen Warren
2012-04-10 8:16 ` [PATCH V4 REPOST 1/5] dt: add property iteration helpers 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='CACRpkdb=8ydKuX52cen8Y_iBzV+RwD61NCPrjQFXNgoO-=bc9Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
/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.