From: Ben Dooks <ben-i2c@fluff.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Thomas Chou <thomas@wytron.com.tw>,
Ben Dooks <ben-linux@fluff.org>,
linux-kernel@vger.kernel.org, nios2-dev@sopc.et.ntust.edu.tw,
devicetree-discuss@lists.ozlabs.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c-ocores: register devices on child nodes
Date: Sun, 20 Feb 2011 23:28:08 +0000 [thread overview]
Message-ID: <20110220232808.GL15795@trinity.fluff.org> (raw)
In-Reply-To: <20110216043540.GB11684@angua.secretlab.ca>
On Tue, Feb 15, 2011 at 09:35:40PM -0700, Grant Likely wrote:
> On Thu, Feb 10, 2011 at 10:51:54AM +0800, Thomas Chou wrote:
> > This patch registers devices on the devicetree child nodes to the bus.
> > Also removes one trailing whitespace.
> >
> > Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
>
> Ben, do you want to pick this one up? Or should I merge it via my
> devicetree branch?
If it applies to the mainline kernel, then I'll take it.
--
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
next prev parent reply other threads:[~2011-02-20 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 2:51 [PATCH] i2c-ocores: register devices on child nodes Thomas Chou
[not found] ` <1297306314-11483-1-git-send-email-thomas-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-02-16 4:35 ` Grant Likely
2011-02-20 23:28 ` Ben Dooks [this message]
[not found] ` <20110220232808.GL15795-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-02-21 3:40 ` Grant Likely
2011-02-23 0:12 ` Ben Dooks
[not found] ` <20110223001252.GT15795-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-02-23 0:31 ` Thomas Chou
[not found] ` <4D645578.3020906-SDxUXYEhEBiCuPEqFHbRBg@public.gmane.org>
2011-02-23 1:07 ` Grant Likely
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=20110220232808.GL15795@trinity.fluff.org \
--to=ben-i2c@fluff.org \
--cc=ben-linux@fluff.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nios2-dev@sopc.et.ntust.edu.tw \
--cc=thomas@wytron.com.tw \
/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).