linux-kernel - Re: Tag on pinctrl

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F96D84E.7080204@wwwdotorg.org>
Date:	Tue, 24 Apr 2012 10:43:58 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	Dong Aisheng <B29396@...escale.com>,
	viresh kumar <viresh.kumar@...com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: Tag on pinctrl

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/