From: Mark Brown <broonie@kernel.org>
To: Nenghua Cao <nhcao@marvell.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] driver: regmap: add regmap_parse_val api
Date: Thu, 6 Mar 2014 17:41:29 +0800 [thread overview]
Message-ID: <20140306094129.GP13126@sirena.org.uk> (raw)
In-Reply-To: <1392806653-29604-1-git-send-email-nhcao@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 559 bytes --]
On Wed, Feb 19, 2014 at 06:44:13PM +0800, Nenghua Cao wrote:
> From: Nenghua Cao <nhcao@marvell.com>
>
> In some cases, we need regmap's format parse_val function
> to do be/le translation according to the bus configuration.
> For example, snd_soc_bytes_put() uses regmap to write/read values,
> and use cpu_to_be() directly to covert MASK into big endian. This
> is a defect, and should use regmap's format function to do it according
> to bus configuration.
Applied, thanks. Please use subject lines matching the style for the
subsystem.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-06 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:44 Nenghua Cao
2014-02-20 8:24 ` Nenghua Cao
2014-02-20 8:55 ` Mark Brown
2014-02-20 12:09 ` Nenghua Cao
2014-02-20 13:42 ` Mark Brown
2014-03-03 10:44 ` Nenghua Cao
2014-03-05 2:03 ` Mark Brown
2014-03-06 9:41 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-19 5:19 Nenghua Cao
2014-02-19 5:28 ` Nenghua Cao
2014-02-19 7:50 ` Mark Brown
2014-02-19 10:50 ` Nenghua Cao
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=20140306094129.GP13126@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhcao@marvell.com \
/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
all inboxes | Powered by JetHome®