From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Initial Tegra ARM support
Date: Tue, 10 Aug 2010 23:06:00 +0100 [thread overview]
Message-ID: <20100810220600.GD7702@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1281476664.9400.36.camel@c-dwalke-linux.qualcomm.com>
On Tue, Aug 10, 2010 at 02:44:24PM -0700, Daniel Walker wrote:
> On Thu, 2010-08-05 at 14:10 -0700, Erik Gilling wrote:
> > Hi Linus,
> >
> > The following changes since commit 9fe6206f400646a2322096b56c59891d530e8d51:
> > Linus Torvalds (1):
> > Linux 2.6.35
> >
> > are available in the git repository at:
> >
> > git://android.kernel.org/kernel/tegra.git for-linus
> >
> > This code has received review on linux-arm-kernel and has been in
> > for-next since June 18th. No subsystems were harmed out side of
> > mach-tegra.
> >
> > Colin Cross (4):
> > [ARM] tegra: Add clock support
> > [ARM] tegra: SMP support
>
>
> This fixes some typos in the Tegra tree which caused build failures in
> all ARM compiles.
Argh, no, not another patch doing this the wrong way. I've fixed this
already, just preparing the pull request for this evening.
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: torvalds@linux-foundation.org, Erik Gilling <konkers@google.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-tegra@vger.kernel.org, davidb@codeaurora.org
Subject: Re: [GIT PULL] Initial Tegra ARM support
Date: Tue, 10 Aug 2010 23:06:00 +0100 [thread overview]
Message-ID: <20100810220600.GD7702@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1281476664.9400.36.camel@c-dwalke-linux.qualcomm.com>
On Tue, Aug 10, 2010 at 02:44:24PM -0700, Daniel Walker wrote:
> On Thu, 2010-08-05 at 14:10 -0700, Erik Gilling wrote:
> > Hi Linus,
> >
> > The following changes since commit 9fe6206f400646a2322096b56c59891d530e8d51:
> > Linus Torvalds (1):
> > Linux 2.6.35
> >
> > are available in the git repository at:
> >
> > git://android.kernel.org/kernel/tegra.git for-linus
> >
> > This code has received review on linux-arm-kernel and has been in
> > for-next since June 18th. No subsystems were harmed out side of
> > mach-tegra.
> >
> > Colin Cross (4):
> > [ARM] tegra: Add clock support
> > [ARM] tegra: SMP support
>
>
> This fixes some typos in the Tegra tree which caused build failures in
> all ARM compiles.
Argh, no, not another patch doing this the wrong way. I've fixed this
already, just preparing the pull request for this evening.
next prev parent reply other threads:[~2010-08-10 22:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:10 [GIT PULL] Initial Tegra ARM support Erik Gilling
2010-08-05 21:10 ` Erik Gilling
2010-08-05 21:45 ` Daniel Walker
2010-08-05 21:45 ` Daniel Walker
2010-08-05 22:01 ` Erik Gilling
2010-08-05 22:01 ` Erik Gilling
2010-08-05 22:06 ` Erik Gilling
2010-08-05 22:06 ` Erik Gilling
2010-08-05 22:14 ` Daniel Walker
2010-08-05 22:14 ` Daniel Walker
2010-08-10 21:44 ` Daniel Walker
2010-08-10 21:44 ` Daniel Walker
2010-08-10 22:06 ` Russell King - ARM Linux [this message]
2010-08-10 22:06 ` Russell King - ARM Linux
2010-08-10 22:10 ` Daniel Walker
2010-08-10 22:10 ` Daniel Walker
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=20100810220600.GD7702@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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.