From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: mc13xxx: add I2C support, V5
Date: Tue, 1 May 2012 12:39:49 +0200 [thread overview]
Message-ID: <20120501103949.GC20224@sortiz-mobl> (raw)
In-Reply-To: <201204170921.42027.marc@cpdesign.com.au>
Hi Marc,
On Tue, Apr 17, 2012 at 09:21:41AM +1000, Marc Reilly wrote:
> Hi Samuel,
>
>
> On Sunday, April 01, 2012 04:41:35 PM Marc Reilly wrote:
> > This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
> > regmap and adds I2C support.
> > It has a compile dependency on regmap/for-next, as the spi driver uses the
> > recently added pad_bits config field.
>
> (bump).
>
> Are these changes OK to go in?
All 4 patches applied to my for-next branch.
I had to manually apply patch #1, please verify that it's all good.
I added an Acked-by: Oskar Schirmer <oskar@scara.com> to patch #4. Please make
sure that you add the right tags to the corresponding patches in the future.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-05-01 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 6:41 mc13xxx: add I2C support, V5 Marc Reilly
2012-04-01 6:41 ` [PATCH v5 1/4] mfd: mc13xxx-core: Prepare for separate spi and i2c backends Marc Reilly
2012-04-01 6:41 ` [PATCH v5 2/4] mfd: mc13xxx-core: use regmap for register access Marc Reilly
2012-04-02 16:00 ` Mark Brown
2012-04-01 6:41 ` [PATCH v5 3/4] mfd: mc13xxx-core: Move spi specific code into separate module Marc Reilly
2012-04-01 6:41 ` [PATCH v5 4/4] mfd: mc13xxx: Add i2c driver Marc Reilly
2012-04-01 9:21 ` mc13xxx: add I2C support, V5 Uwe Kleine-König
[not found] ` <201204011939.49665.marc@cpdesign.com.au>
2012-04-02 6:40 ` Uwe Kleine-König
2012-04-01 11:12 ` Alex Gershgorin
2012-04-16 23:21 ` Marc Reilly
2012-05-01 10:39 ` Samuel Ortiz [this message]
2012-05-01 22:55 ` Marc Reilly
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=20120501103949.GC20224@sortiz-mobl \
--to=sameo@linux.intel.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