From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marc Reilly <marc@cpdesign.com.au>
Cc: sameo@linux.intel.com, linux-arm-kernel@lists.infradead.org,
spi-devel-general@lists.sourceforge.net,
linux-i2c@vger.kernel.org, u.kleine-koenig@pengutronix.de,
oskar@scara.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/6] regmap: Add support for device with 24 data bits.
Date: Thu, 15 Mar 2012 10:46:18 +0000 [thread overview]
Message-ID: <20120315104617.GD3138@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1331757790-10583-3-git-send-email-marc@cpdesign.com.au>
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
On Thu, Mar 15, 2012 at 07:43:06AM +1100, Marc Reilly wrote:
> Add support for devices with 24 data bits.
Not sure what you generated this patch against but it doesn't apply to
my topic/core or against -next. Please regenerate it against
topic/core, it looks good.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-15 10:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 20:43 mc13xxx: add I2C support (now with regmap), V3 Marc Reilly
2012-03-14 20:43 ` [PATCH v3 1/6] regmap: add support for 7_25 format Marc Reilly
2012-03-15 10:44 ` Mark Brown
2012-03-14 20:43 ` [PATCH v3 2/6] regmap: Add support for device with 24 data bits Marc Reilly
2012-03-15 10:46 ` Mark Brown [this message]
2012-03-14 20:43 ` [PATCH v3 3/6] mfd: mc13xxx-core: Prepare for separate spi and i2c backends Marc Reilly
2012-03-14 20:43 ` [PATCH v3 4/6] mfd: mc13xxx-core: use regmap for register access Marc Reilly
2012-03-15 17:43 ` Mark Brown
2012-03-14 20:43 ` [PATCH v3 5/6] mfd: mc13xxx-core: Move spi specific code into separate module Marc Reilly
2012-03-14 20:43 ` [PATCH v3 6/6] mfd: mc13xxx: Add i2c driver Marc Reilly
2012-03-14 22:15 ` Fabio Estevam
2012-03-15 13:40 ` Shubhrajyoti Datta
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=20120315104617.GD3138@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@cpdesign.com.au \
--cc=oskar@scara.com \
--cc=sameo@linux.intel.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=u.kleine-koenig@pengutronix.de \
/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