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: <20120425104559.GA16752@sirena.org.uk>
Date:	Wed, 25 Apr 2012 11:46:00 +0100
From:	Mark Brown <broonie@...ena.org.uk>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Dong Aisheng <B29396@...escale.com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: Tag on pinctrl

On Tue, Apr 24, 2012 at 10:43:58AM -0600, Stephen Warren wrote:

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

If the gpio-pinmux branch is based on Linus' branch (which it really
should be if it's a dependency...) then git will do the right thing
here.  If it's not then you need to explicitly get things pulled in but
there will also be bisection issues.
--
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/