From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: i2c-ocores changes (version 2)
Date: Thu, 23 Dec 2010 21:03:20 -0700 [thread overview]
Message-ID: <20101224040320.GF2491@angua.secretlab.ca> (raw)
In-Reply-To: <4CFC67AA.2080707-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
On Mon, Dec 06, 2010 at 04:33:46AM +0000, Ben Dooks wrote:
> On 24/11/10 16:26, Jonas Bonn wrote:
> > Version 2 of patch series incorporating initial feedback from review.
> >
> > /Jonas
>
> I'm relatively happy with this.
> Any comments from the devicetree side?
Patches 1 & 2 look good to me. Some comments on the 3rd patch.
Acked-by: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
prev parent reply other threads:[~2010-12-24 4:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 16:26 i2c-ocores changes (version 2) Jonas Bonn
[not found] ` <1290615982-1028-1-git-send-email-jonas-A9uVI2HLR7kOP4wsBPIw7w@public.gmane.org>
2010-11-24 16:26 ` [PATCH 1/3] i2c-ocores: Adapt for device tree Jonas Bonn
[not found] ` <1290615982-1028-2-git-send-email-jonas-A9uVI2HLR7kOP4wsBPIw7w@public.gmane.org>
2011-01-04 1:05 ` Ben Dooks
2010-11-24 16:26 ` [PATCH 2/3] i2c-ocores: Use devres for resource allocation Jonas Bonn
2010-11-24 16:26 ` [PATCH 3/3] i2c-ocores: add some device tree documentation Jonas Bonn
[not found] ` <1290615982-1028-4-git-send-email-jonas-A9uVI2HLR7kOP4wsBPIw7w@public.gmane.org>
2010-12-24 4:00 ` Grant Likely
[not found] ` <20101224040017.GE2491-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2010-12-24 9:38 ` Jonas Bonn
2010-12-24 14:02 ` Peter Korsgaard
2010-12-24 20:06 ` Grant Likely
2010-12-06 4:33 ` i2c-ocores changes (version 2) Ben Dooks
[not found] ` <4CFC67AA.2080707-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
2010-12-24 4:03 ` Grant Likely [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=20101224040320.GF2491@angua.secretlab.ca \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).