From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Tag on pinctrl
Date: Tue, 24 Apr 2012 10:43:58 -0600 [thread overview]
Message-ID: <4F96D84E.7080204@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdYqZrNFxj4kyMqYZk5PAcjF6-TroJ+Xq+3EVBLvo5Zg-Q@mail.gmail.com>
On 04/24/2012 07:15 AM, Linus Walleij wrote:
> A while back I created a tag:
>
> pinctrl-mergebase-20120418
>
> On the pinctrl tree. It contains stuff up until that date that
> has since been sitting in linux-next for a while.
>
> I do not expect to rebase these patches further. They
> are based on v3.4-rc3. So I will base any further pinctrl
> work on this.
>
> I think Stephen needed to pull this into the ARM SoC tree?
Yes, I have pulled that tag into the Tegra tree as
for-3.5/gpio-pinmux-dependency, and have a Tegra-specific
for-3.5/gpio-pinmux branch that depends on it. Two other Tegra branches
in turn (for-3.5/tegra30-audio, for-3.5/usb-ulpi) depend on
for-3.5/gpio-pinmux.
Linus, I think this will get into the ARM SoC tree simply by my saying
in my for-3.5/gpio-pinmux pull request that the branch depends on your
tag; I don't /think/ you need to explicitly send a pull request there,
right?
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dong Aisheng <B29396@freescale.com>,
viresh kumar <viresh.kumar@st.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: Tag on pinctrl
Date: Tue, 24 Apr 2012 10:43:58 -0600 [thread overview]
Message-ID: <4F96D84E.7080204@wwwdotorg.org> (raw)
In-Reply-To: <CACRpkdYqZrNFxj4kyMqYZk5PAcjF6-TroJ+Xq+3EVBLvo5Zg-Q@mail.gmail.com>
On 04/24/2012 07:15 AM, Linus Walleij wrote:
> A while back I created a tag:
>
> pinctrl-mergebase-20120418
>
> On the pinctrl tree. It contains stuff up until that date that
> has since been sitting in linux-next for a while.
>
> I do not expect to rebase these patches further. They
> are based on v3.4-rc3. So I will base any further pinctrl
> work on this.
>
> I think Stephen needed to pull this into the ARM SoC tree?
Yes, I have pulled that tag into the Tegra tree as
for-3.5/gpio-pinmux-dependency, and have a Tegra-specific
for-3.5/gpio-pinmux branch that depends on it. Two other Tegra branches
in turn (for-3.5/tegra30-audio, for-3.5/usb-ulpi) depend on
for-3.5/gpio-pinmux.
Linus, I think this will get into the ARM SoC tree simply by my saying
in my for-3.5/gpio-pinmux pull request that the branch depends on your
tag; I don't /think/ you need to explicitly send a pull request there,
right?
next prev parent reply other threads:[~2012-04-24 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 13:15 Tag on pinctrl Linus Walleij
2012-04-24 13:15 ` Linus Walleij
2012-04-24 16:43 ` Stephen Warren [this message]
2012-04-24 16:43 ` Stephen Warren
2012-04-25 10:46 ` Mark Brown
2012-04-25 10:46 ` Mark Brown
2012-04-25 15:01 ` Stephen Warren
2012-04-25 15:01 ` Stephen Warren
2012-04-25 11:22 ` Linus Walleij
2012-04-25 11:22 ` 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=4F96D84E.7080204@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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.