From: pdeschrijver@nvidia.com (Peter De Schrijver)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/3] Add support for tegra2 based ventana board
Date: Thu, 13 Oct 2011 16:07:07 +0300 [thread overview]
Message-ID: <20111013130707.GM1001@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <20111012223643.GA5368@quad.lixom.net>
On Thu, Oct 13, 2011 at 12:36:43AM +0200, Olof Johansson wrote:
> On Wed, Oct 12, 2011 at 08:56:47AM -0700, Stephen Warren wrote:
> > pdeschrijver at nvidia.com wrote at Wednesday, October 12, 2011 5:53 AM:
> > > This patch set adds support for the tegra2 based ventana development board.
> > >
> > > Boot tested on ventana.
> > >
> > > Uses a table based approach to select the correct init function.
> > >
> > > Provoke kernel warning when no suitable pinmux table can be found.
> >
> > Whole series:
> >
> > Acked-by: Stephen Warren <swarren@nvidia.com>
> >
> > Thanks for following up on my picky comments:-)
>
> Yes, thanks Peter.
>
> Applied to for-3.2/features. I had to do some fixups since I applied it
> on top of some of Stephen's changes for gpio/pinmux, so please verify
> that I did the fixups correctly.
I just booted your tree on ventana. Works fine! Thanks!
Peter.
prev parent reply other threads:[~2011-10-13 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 11:53 [PATCH v9 0/3] Add support for tegra2 based ventana board pdeschrijver at nvidia.com
2011-10-12 11:53 ` [PATCH v9 1/3] arm/tegra: prepare Seaboard pinmux code for derived boards pdeschrijver at nvidia.com
2011-10-12 11:53 ` [PATCH v9 2/3] arm/tegra: add support for ventana pinmuxing pdeschrijver at nvidia.com
2011-10-12 11:53 ` [PATCH v9 3/3] arm/tegra: device tree support for ventana board pdeschrijver at nvidia.com
2011-10-12 15:56 ` [PATCH v9 0/3] Add support for tegra2 based " Stephen Warren
2011-10-12 22:36 ` Olof Johansson
2011-10-13 13:07 ` Peter De Schrijver [this message]
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=20111013130707.GM1001@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--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).