All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ARM kernel mailing list
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Tegra for-next branch status check
Date: Mon, 23 Apr 2012 15:21:13 -0600	[thread overview]
Message-ID: <4F95C7C9.30205@wwwdotorg.org> (raw)

Arnd, Olof,

Could I please ask you to take a quick look at Tegra's git repo:

git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git

... and double-check the construction of all the for-3.5 branches. I've
tended to mostly put stuff in topic branches rather than separating
things into the perhaps more typical soc/drivers/dt branches. Is this
scheme going to work out OK?

Note a couple dependencies in there:

for-3.5/gpio-pinmux-dependency is a copy of pinctrl's "base" tag.

for-3.5/gpio-pinmux depends on for-3.5/gpio-pinmux-dependency

for-3.5/tegra30-audio and for-3.5/usb-ulpi both depend on
for-3.5/gpio-pinmux.

Thanks for any feedback.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra for-next branch status check
Date: Mon, 23 Apr 2012 15:21:13 -0600	[thread overview]
Message-ID: <4F95C7C9.30205@wwwdotorg.org> (raw)

Arnd, Olof,

Could I please ask you to take a quick look at Tegra's git repo:

git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git

... and double-check the construction of all the for-3.5 branches. I've
tended to mostly put stuff in topic branches rather than separating
things into the perhaps more typical soc/drivers/dt branches. Is this
scheme going to work out OK?

Note a couple dependencies in there:

for-3.5/gpio-pinmux-dependency is a copy of pinctrl's "base" tag.

for-3.5/gpio-pinmux depends on for-3.5/gpio-pinmux-dependency

for-3.5/tegra30-audio and for-3.5/usb-ulpi both depend on
for-3.5/gpio-pinmux.

Thanks for any feedback.

             reply	other threads:[~2012-04-23 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 21:21 Stephen Warren [this message]
2012-04-23 21:21 ` Tegra for-next branch status check Stephen Warren
     [not found] ` <4F95C7C9.30205-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-04-25 18:21   ` Olof Johansson
2012-04-25 18:21     ` Olof Johansson

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=4F95C7C9.30205@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.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.