From: Olof Johansson <olof@lixom.net>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Russell King <linux@arm.linux.org.uk>,
Colin Cross <ccross@android.com>,
Stephen Warren <swarren@nvidia.com>, Gary King <gking@nvidia.com>,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v7 00/14] Add support for tegra30 and cardhu
Date: Sat, 17 Dec 2011 20:48:31 -0800 [thread overview]
Message-ID: <20111218044831.GB4336@quad.lixom.net> (raw)
In-Reply-To: <1323875032-18221-1-git-send-email-pdeschrijver@nvidia.com>
On Wed, Dec 14, 2011 at 05:03:12PM +0200, Peter De Schrijver wrote:
> This patchset adds support for the tegra30 SoC and the cardhu development
> board.
Thanks, applied to for-3.3/dt (first patch) and for-3.3/soc (the rest).
I didn't want to split up too much between the branches and make
cross-dependencies since that defeats most of the idea behind topic branches,
so I left it at that.
I rebased for-3.3/soc (which only had one patch on it before) to be on top of
rmk's devel-stable and for-3.3/dt, and will tell Arnd about those dependencies
when sending up the branches -- other SoCs have similar dependencies already so
it's not a problem.
I had to do some minor touchups, including redoing the move of board-dt.c due
to other changes to the file. Please check final contents of the branch and let
me know if there's a problem.
Also, the defconfig needs to be updated to enable t30 support as well as move
over to the new config option for t20. I'll post a patch in a few minutes.
Please let me know how the branch looks as soon as practical, since the
clock is ticking on getting the branches into arm-soc in the next few
days for the upcoming merge window.
-Olof
next prev parent reply other threads:[~2011-12-18 4:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 15:03 [PATCH v7 00/14] Add support for tegra30 and cardhu Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 01/14] arm/tegra: initial device tree for tegra30 Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 04/14] arm/tegra: don't export clk_measure_input_freq Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 06/14] arm/tegra: rename board-dt.c to board-dt-tegra20.c Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 07/14] arm/tegra: use PMC reset Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 08/14] arm/tegra: generalize L2 cache initialization Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 09/14] arm/tegra: rename tegra20 pinmux files Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 10/14] arm/tegra: prepare pinmux code for multiple tegra variants Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 11/14] arm/tegra: add new fields to struct tegra_pingroup_desc Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 13/14] arm/tegra: implement support for tegra30 Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 14/14] arm/tegra: add support for tegra30 based board cardhu Peter De Schrijver
[not found] ` <1323875032-18221-1-git-send-email-pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-12-14 15:03 ` [PATCH v7 02/14] arm/tegra: cleanup tegra20 support Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 03/14] arm/tegra: prepare clock code for multiple tegra variants Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 05/14] arm/tegra: prepare early init " Peter De Schrijver
2011-12-14 15:03 ` [PATCH v7 12/14] arm/tegra: pinmux tables and definitions for tegra30 Peter De Schrijver
2011-12-15 18:16 ` [PATCH v7 00/14] Add support for tegra30 and cardhu Olof Johansson
2011-12-15 22:06 ` Colin Cross
2011-12-15 20:54 ` Stephen Warren
2011-12-18 4:48 ` Olof Johansson [this message]
2011-12-19 12:21 ` Peter De Schrijver
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=20111218044831.GB4336@quad.lixom.net \
--to=olof@lixom.net \
--cc=ccross@android.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gking@nvidia.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pdeschrijver@nvidia.com \
--cc=rdunlap@xenotime.net \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.com \
/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