linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/4] add syscon driver based on regmap for general registers access
Date: Mon, 17 Sep 2012 15:30:54 +0200	[thread overview]
Message-ID: <20120917133054.GT3647@sortiz-mobl> (raw)
In-Reply-To: <20120917101028.GA13226@shlinux2.ap.freescale.net>

Hi Dong,

On Mon, Sep 17, 2012 at 06:10:29PM +0800, Dong Aisheng wrote:
> Hi Samuel,
> 
> On Wed, Sep 05, 2012 at 01:54:12PM +0800, Shawn Guo wrote:
> > Hi Samuel,
> > 
> > The series needs to go via mfd or arm-soc tree as a whole.  In case
> > you want to take it through mfd tree, here is my ack.
> > 
> > Acked-by: Shawn Guo <shawn.guo@linaro.org>
> > 
> > Otherwise, I can take it via arm-soc tree with your ack.
> > 
> Ping...
All 4 patches applied to my for-next branch. Sorry for the delay.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2012-09-17 13:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  2:57 [PATCH v6 0/4] add syscon driver based on regmap for general registers access Dong Aisheng
2012-09-05  2:57 ` [PATCH v6 1/4] mfd: add syscon driver based on regmap Dong Aisheng
2012-09-05  2:57 ` [PATCH v6 2/4] ARM: imx6q: add iomuxc gpr support into syscon Dong Aisheng
2012-09-05  2:57 ` [PATCH v6 3/4] regulator: anatop-regulator: convert to use syscon to access anatop register Dong Aisheng
2012-09-05  2:57 ` [PATCH v6 4/4] mfd: anatop-mfd: remove anatop driver Dong Aisheng
2012-09-05  5:54 ` [PATCH v6 0/4] add syscon driver based on regmap for general registers access Shawn Guo
2012-09-17 10:10   ` Dong Aisheng
2012-09-17 13:30     ` Samuel Ortiz [this message]
2012-09-18  1:33       ` Dong Aisheng

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=20120917133054.GT3647@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).