From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] mfd: anatop: make register accessor more flexible and rename meaningfully
Date: Fri, 18 May 2012 11:09:54 +0200 [thread overview]
Message-ID: <20120518090954.GC12015@sortiz-mobl> (raw)
In-Reply-To: <1336871882-6796-1-git-send-email-richard.zhao@freescale.com>
Hi Richard,
On Sun, May 13, 2012 at 09:18:02AM +0800, Richard Zhao wrote:
> - rename to anatop_read_reg and anatop_write_reg
> - anatop_read_reg directly return reg value
> - anatop_write_reg write reg with mask
Patch applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
WARNING: multiple messages have this Message-ID (diff)
From: Samuel Ortiz <sameo@linux.intel.com>
To: Richard Zhao <richard.zhao@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, paul.liu@linaro.org,
broonie@opensource.wolfsonmicro.com, shawn.guo@linaro.org,
Richard Zhao <richard.zhao@freescale.com>
Subject: Re: [PATCH V2] mfd: anatop: make register accessor more flexible and rename meaningfully
Date: Fri, 18 May 2012 11:09:54 +0200 [thread overview]
Message-ID: <20120518090954.GC12015@sortiz-mobl> (raw)
In-Reply-To: <1336871882-6796-1-git-send-email-richard.zhao@freescale.com>
Hi Richard,
On Sun, May 13, 2012 at 09:18:02AM +0800, Richard Zhao wrote:
> - rename to anatop_read_reg and anatop_write_reg
> - anatop_read_reg directly return reg value
> - anatop_write_reg write reg with mask
Patch applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-05-18 9:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 0:59 [PATCH 1/2] mfd: anatop: make register accessor more flexible and rename meaningfully Richard Zhao
2012-05-13 0:59 ` Richard Zhao
2012-05-13 0:59 ` [PATCH 2/2] mfd: anatop: permit adata be NULL when access register Richard Zhao
2012-05-13 0:59 ` Richard Zhao
2012-05-14 3:51 ` Shawn Guo
2012-05-14 3:51 ` Shawn Guo
2012-05-14 8:08 ` Mark Brown
2012-05-14 8:08 ` Mark Brown
2012-05-14 8:48 ` Shawn Guo
2012-05-14 8:48 ` Shawn Guo
2012-05-14 9:01 ` Ying-Chun Liu (PaulLiu)
2012-05-14 9:01 ` Ying-Chun Liu (PaulLiu)
2012-05-14 9:43 ` Shawn Guo
2012-05-14 9:43 ` Shawn Guo
2012-05-14 13:26 ` Ying-Chun Liu (PaulLiu)
2012-05-14 13:26 ` Ying-Chun Liu (PaulLiu)
2012-05-14 13:50 ` Richard Zhao
2012-05-14 13:50 ` Richard Zhao
2012-05-18 9:59 ` Richard Zhao
2012-05-18 9:59 ` Richard Zhao
2012-05-21 4:13 ` Shawn Guo
2012-05-21 4:13 ` Shawn Guo
2012-05-21 9:27 ` Ying-Chun Liu (PaulLiu)
2012-05-21 9:27 ` Ying-Chun Liu (PaulLiu)
2012-05-21 9:39 ` Richard Zhao
2012-05-21 9:39 ` Richard Zhao
2012-06-18 20:23 ` Rob Lee
2012-06-18 20:23 ` Rob Lee
2012-06-18 21:58 ` Samuel Ortiz
2012-06-18 21:58 ` Samuel Ortiz
2012-06-18 22:59 ` Rob Lee
2012-06-18 22:59 ` Rob Lee
2012-05-13 1:18 ` [PATCH V2] mfd: anatop: make register accessor more flexible and rename meaningfully Richard Zhao
2012-05-13 1:18 ` Richard Zhao
2012-05-13 17:48 ` Ying-Chun Liu (PaulLiu)
2012-05-13 17:48 ` Ying-Chun Liu (PaulLiu)
2012-05-18 9:09 ` Samuel Ortiz [this message]
2012-05-18 9:09 ` Samuel Ortiz
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=20120518090954.GC12015@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 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.