public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Dong Aisheng <B29396@freescale.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Tag on pinctrl
Date: Wed, 25 Apr 2012 09:01:57 -0600	[thread overview]
Message-ID: <4F9811E5.4040105@wwwdotorg.org> (raw)
In-Reply-To: <20120425104559.GA16752@sirena.org.uk>

On 04/25/2012 04:46 AM, Mark Brown wrote:
> 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.

The Tegra branch is indeed based directly on the pinctrl branch.

However, I was talking more about how Arnd/Olof are managing arm-soc
than raw git operation; I believe they like to keep an explicit separate
branch for each dependency in order to track which commits to wait for
before sending pull requests for the branches they have that are based
on them, so the dependent commits come in from their original subsystem
first.

  reply	other threads:[~2012-04-25 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 13:15 Tag on pinctrl Linus Walleij
2012-04-24 16:43 ` Stephen Warren
2012-04-25 10:46   ` Mark Brown
2012-04-25 15:01     ` Stephen Warren [this message]
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=4F9811E5.4040105@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=B29396@freescale.com \
    --cc=broonie@sirena.org.uk \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox