From: Stephen Warren <swarren@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Erik Gilling <konkers@android.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v7 0/3] Add support for tegra2 based ventana board
Date: Fri, 7 Oct 2011 11:00:55 -0700 [thread overview]
Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF173B23B2F1@HQMAIL01.nvidia.com> (raw)
In-Reply-To: <1317647918-22694-1-git-send-email-pdeschrijver@nvidia.com>
Peter De Schrijver wrote at Monday, October 03, 2011 7:19 AM:
> This patch set adds support for the tegra2 based ventana development board.
>
> Boot tested on ventana.
With minor changes to the command-line in tegra-ventana.dts, to put the
root fs on an SD card, and using mainline U-Boot with the Ventana patch
series I wrote,
Tested-by: Stephen Warren <swarren@nvidia.com>
I have a couple of queries in patch 3 that I'll post separately.
--
nvpublic
next prev parent reply other threads:[~2011-10-07 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 13:18 Peter De Schrijver
2011-10-03 13:18 ` [PATCH v7 1/3] arm/tegra: prepare Seaboard pinmux code for derived boards Peter De Schrijver
2011-10-03 13:18 ` [PATCH v7 2/3] arm/tegra: add support for ventana pinmuxing Peter De Schrijver
2011-10-03 13:18 ` [PATCH v7 3/3] arm/tegra: device tree support for ventana board Peter De Schrijver
2011-10-07 18:04 ` Stephen Warren
2011-10-10 8:01 ` Peter De Schrijver
2011-10-10 16:38 ` Stephen Warren
2011-10-07 18:00 ` Stephen Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-03 13:17 [PATCH v7 0/3] Add support for tegra2 based " Peter De Schrijver
2011-10-03 13:19 ` 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=74CDBE0F657A3D45AFBB94109FB122FF173B23B2F1@HQMAIL01.nvidia.com \
--to=swarren@nvidia.com \
--cc=ccross@android.com \
--cc=konkers@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=pdeschrijver@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
all inboxes | Powered by JetHome®