From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] [ARM] tegra: Additional core support for Tegra2 SOCs
Date: Thu, 2 Sep 2010 09:48:12 +0100 [thread overview]
Message-ID: <20100902084812.GD26319@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTinhoBrzYmypsKNcLPar-pKWiYm60GL6YBfd1jT9@mail.gmail.com>
On Wed, Aug 25, 2010 at 02:24:24PM -0700, Erik Gilling wrote:
> Any comments on the below patches? If not I'm going to push them to
> our for-next tree.
Where are the patches? I don't see them on the mailing list. We don't
review code sitting in git trees - only patches on mailing lists.
next prev parent reply other threads:[~2010-09-02 8:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 0:29 [PATCH 0/9] [ARM] tegra: Additional core support for Tegra2 SOCs Colin Cross
2010-07-30 0:29 ` [PATCH 1/9] [ARM] tegra: update iomap Colin Cross
2010-07-30 0:29 ` [PATCH 2/9] [ARM] tegra: Add legacy irq support Colin Cross
2010-07-30 0:29 ` [PATCH 3/9] [ARM] tegra: add suspend and mirror irqs to legacy controller Colin Cross
2010-07-30 0:29 ` [PATCH 4/9] [ARM] tegra: pinmux: add safe values, move tegra2, add suspend Colin Cross
2010-07-30 0:29 ` [PATCH 5/9] [ARM] tegra: gpio: Add suspend and wake support Colin Cross
2010-07-30 0:29 ` [PATCH 6/9] [ARM] tegra: Add support for reading fuses Colin Cross
2010-07-30 0:29 ` [PATCH 7/9] [ARM] tegra: clock: Add dvfs support, bug fixes, and cleanups Colin Cross
2010-07-30 0:29 ` [PATCH 8/9] [ARM] tegra: common: Update common clock init table Colin Cross
2010-07-30 0:29 ` [PATCH 9/9] [ARM] tegra: Add cpufreq support Colin Cross
2010-07-30 13:11 ` Dominik Brodowski
2010-07-30 19:56 ` Colin Cross
2010-07-30 20:20 ` Mark Brown
2010-07-30 20:33 ` Colin Cross
2010-07-30 21:14 ` Mark Brown
2010-08-25 21:24 ` [PATCH 0/9] [ARM] tegra: Additional core support for Tegra2 SOCs Erik Gilling
2010-09-01 22:14 ` Erik Gilling
2010-09-02 8:48 ` Russell King - ARM Linux [this message]
2010-09-02 10:20 ` Erik Gilling
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=20100902084812.GD26319@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 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).