From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] staging: nvec: add device tree support
Date: Wed, 9 Nov 2011 11:57:55 -0800 [thread overview]
Message-ID: <20111109195755.GA7052@suse.de> (raw)
In-Reply-To: <20111109191144.GB5354@quad.lixom.net>
On Wed, Nov 09, 2011 at 11:11:44AM -0800, Olof Johansson wrote:
> On Tue, Nov 01, 2011 at 03:36:31PM -0700, Stephen Warren wrote:
> > Marc Dietrich wrote at Tuesday, November 01, 2011 2:37 PM:
> > > This adds device tree support to the nvec driver. By using this method
> > > it is no longer necessary to specify platform data through a board
> > > file.
> >
> > Acked-by: Stephen Warren <swarren@nvidia.com>
>
> Acked-by: Olof Johansson <olof@lixom.net>
>
> Greg, this one can go through the staging tree. We'll pick up the other pieces
> of the series through the tegra soc tree.
Ok, will do.
greg k-h
next prev parent reply other threads:[~2011-11-09 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 20:37 [PATCH v4 0/3] paz00 updates for 3.3 Marc Dietrich
2011-11-01 20:37 ` [PATCH 1/3] ARM: tegra: paz00: add support for wakeup gpio key Marc Dietrich
2011-11-01 20:37 ` [PATCH 2/3] staging: nvec: add device tree support Marc Dietrich
2011-11-01 22:36 ` Stephen Warren
2011-11-09 19:11 ` Olof Johansson
2011-11-09 19:57 ` Greg KH [this message]
2011-11-21 13:42 ` Marc Dietrich
2011-11-01 20:37 ` [PATCH 3/3] arm/dt: tegra: add dts file for paz00 Marc Dietrich
2011-11-01 22:37 ` Stephen Warren
-- strict thread matches above, loose matches on Subject: below --
2011-10-31 19:58 [PATCH v3 0/3] paz00 updates for 3.3 Marc Dietrich
2011-10-31 19:58 ` [PATCH 2/3] staging: nvec: add device tree support Marc Dietrich
2011-10-31 20:18 ` Stephen Warren
2011-10-31 22:18 ` Marc Dietrich
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=20111109195755.GA7052@suse.de \
--to=gregkh@suse.de \
--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).