From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Add device tree probe for i2c-mxs driver
Date: Sat, 12 May 2012 19:17:35 +0800 [thread overview]
Message-ID: <CAAQ0ZWSpSsj5cXRU4BmxYiKum6t6FceC-=rGqFKFN8hmBpD+VA@mail.gmail.com> (raw)
In-Reply-To: <20120512110732.GD20673@pengutronix.de>
On 12 May 2012 19:07, Wolfram Sang <w.sang@pengutronix.de> wrote:
> Patch 1/2:
>
> Acked-by: Wolfram Sang <w.sang@pengutronix.de>
>
Thanks, Wolfram. Just updated branch mxs/dt/for-3.5 with the tag collected.
Regards,
Shawn
prev parent reply other threads:[~2012-05-12 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 7:31 [PATCH 0/2] Add device tree probe for i2c-mxs driver Shawn Guo
2012-05-10 7:31 ` [PATCH 1/2] i2c: mxs: add device tree probe support Shawn Guo
2012-05-10 7:31 ` [PATCH 2/2] ARM: dts: enable i2c device for imx28-evk Shawn Guo
2012-05-12 11:07 ` [PATCH 0/2] Add device tree probe for i2c-mxs driver Wolfram Sang
2012-05-12 11:17 ` Shawn Guo [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='CAAQ0ZWSpSsj5cXRU4BmxYiKum6t6FceC-=rGqFKFN8hmBpD+VA@mail.gmail.com' \
--to=shawn.guo@linaro.org \
--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).