linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] ARM: tegra: for-3.5/ahb branch
Date: Mon, 14 May 2012 20:55:12 +0000	[thread overview]
Message-ID: <201205142055.12881.arnd@arndb.de> (raw)
In-Reply-To: <1337024794-25269-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On Monday 14 May 2012, Stephen Warren wrote:
> I meant to send this with the other two pull requests this morning, but
> forgot:-(
> 
> This is the last pull request I intend to send for 3.5, except for any
> bugs that crop up.
> 
> ----------------------------------------------------------------
> 
> The following changes since commit e816b57a337ea3b755de72bec38c10c864f23015:
> 
>   Linux 3.4-rc3
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git for-3.5/ahb
> 
> for you to fetch changes up to 89c788bab1f0374ae05aef7560066442ceb55384:
> 
>   ARM: tegra: Add SMMU enabler in AHB
> 

When I pull the branch, I get an extraneous commit
"ARM: dt: tegra: Add device tree support for AHB" that adds nodes that are
already there from another branch. I've removed that commit and applied the
rest to next/drivers. Please check what I have now.

Thanks,

	Arnd

  parent reply	other threads:[~2012-05-14 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 19:46 [GIT PULL] ARM: tegra: for-3.5/ahb branch Stephen Warren
     [not found] ` <1337024794-25269-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-14 20:55   ` Arnd Bergmann [this message]
     [not found]     ` <201205142055.12881.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-14 21:03       ` Stephen Warren

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=201205142055.12881.arnd@arndb.de \
    --to=arnd-r2ngtmty4d4@public.gmane.org \
    --cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).