From: Samuel Ortiz <sameo@linux.intel.com>
To: Rob Lee <rob.lee@linaro.org>
Cc: Richard Zhao <richard.zhao@freescale.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
Shawn Guo <shawn.guo@freescale.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org, shawn.guo@linaro.org,
Richard Zhao <richard.zhao@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] mfd: anatop: permit adata be NULL when access register
Date: Mon, 18 Jun 2012 23:58:47 +0200 [thread overview]
Message-ID: <20120618215847.GU7147@sortiz-mobl> (raw)
In-Reply-To: <CAMXH7KF4qegQkQ3mS2=U=VBXZHJfiU2GiozRHgkP3OVX0Q+thQ@mail.gmail.com>
Hi Rob,
On Mon, Jun 18, 2012 at 03:23:45PM -0500, Rob Lee wrote:
> Hi,
>
> What is the status of this patch?
I'm swamped with other things to look at right now, but I expect to clean my
MFD patches backlog at the beginning of next week.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-06-18 21:48 UTC|newest]
Thread overview: 19+ 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 ` [PATCH 2/2] mfd: anatop: permit adata be NULL when access register Richard Zhao
2012-05-14 3:51 ` Shawn Guo
2012-05-14 8:08 ` Mark Brown
2012-05-14 8:48 ` Shawn Guo
2012-05-14 9:01 ` Ying-Chun Liu (PaulLiu)
2012-05-14 9:43 ` Shawn Guo
2012-05-14 13:26 ` Ying-Chun Liu (PaulLiu)
2012-05-14 13:50 ` Richard Zhao
2012-05-18 9:59 ` Richard Zhao
2012-05-21 4:13 ` Shawn Guo
2012-05-21 9:27 ` Ying-Chun Liu (PaulLiu)
2012-05-21 9:39 ` Richard Zhao
2012-06-18 20:23 ` Rob Lee
2012-06-18 21:58 ` Samuel Ortiz [this message]
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 17:48 ` Ying-Chun Liu (PaulLiu)
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=20120618215847.GU7147@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.liu@linaro.org \
--cc=richard.zhao@freescale.com \
--cc=richard.zhao@linaro.org \
--cc=rob.lee@linaro.org \
--cc=shawn.guo@freescale.com \
--cc=shawn.guo@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox