From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marc Reilly <marc@cpdesign.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] regmap: Add support for device with 24 data bits.
Date: Sat, 17 Mar 2012 22:06:26 +0000 [thread overview]
Message-ID: <20120317220626.GJ3315@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1331860303-9483-1-git-send-email-marc@cpdesign.com.au>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
On Fri, Mar 16, 2012 at 12:11:42PM +1100, Marc Reilly wrote:
> Add support for devices with 24 data bits.
Applied both, thanks. I'm not sure if I'll send them for 3.4 or not,
obviously we're very close to the merge window opening (I'm actually
surprised it isn't open already), but since there's no external
interface changes it shouldn't create merge issues for the MFD.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-03-17 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 1:11 [PATCH 1/2] regmap: Add support for device with 24 data bits Marc Reilly
2012-03-16 1:11 ` [PATCH 2/2] regmap: Use pad_bits and reg_bits when determining register format Marc Reilly
2012-03-17 22:06 ` Mark Brown [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=20120317220626.GJ3315@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@cpdesign.com.au \
/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