From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regmap: Add 24 bits support
Date: Mon, 26 Mar 2012 15:50:55 +0100 [thread overview]
Message-ID: <20120326145054.GV3098@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332772808-13346-1-git-send-email-alexg@meprolight.com>
On Mon, Mar 26, 2012 at 04:40:08PM +0200, Alex Gershgorin wrote:
> This patch adds support for PMIC who use regmap and 24 bit registers
> For example MC13892, the patch was tested on i.MX35-PDK
A similar patch from Marc Reilly has already been applied. You don't
have his signoff here but then...
> +typedef struct { __u8 b[3]; } __be24;
...you're adding stuff like this to the regmap headers which *clearly*
isn't regmap specific so this looks like a separate development.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120326/29610d5f/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alex Gershgorin <alexg@meprolight.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, marc.reilly@gmail.com,
s.hauer@pengutronix.de, fabio.estevam@freescale.com
Subject: Re: [PATCH] regmap: Add 24 bits support
Date: Mon, 26 Mar 2012 15:50:55 +0100 [thread overview]
Message-ID: <20120326145054.GV3098@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1332772808-13346-1-git-send-email-alexg@meprolight.com>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
On Mon, Mar 26, 2012 at 04:40:08PM +0200, Alex Gershgorin wrote:
> This patch adds support for PMIC who use regmap and 24 bit registers
> For example MC13892, the patch was tested on i.MX35-PDK
A similar patch from Marc Reilly has already been applied. You don't
have his signoff here but then...
> +typedef struct { __u8 b[3]; } __be24;
...you're adding stuff like this to the regmap headers which *clearly*
isn't regmap specific so this looks like a separate development.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-26 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 14:40 [PATCH] regmap: Add 24 bits support Alex Gershgorin
2012-03-26 14:40 ` Alex Gershgorin
2012-03-26 14:50 ` Mark Brown [this message]
2012-03-26 14:50 ` Mark Brown
2012-03-26 17:30 ` Alex Gershgorin
2012-03-26 17:30 ` Alex Gershgorin
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=20120326145054.GV3098@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.