From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/2] mfd: Mark WM1811 GPIO6 register volatile for later revisions
Date: Mon, 19 Dec 2011 12:17:02 +0100 [thread overview]
Message-ID: <20111219111702.GC11800@sortiz-mobl> (raw)
In-Reply-To: <1322747814-31877-2-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Thu, Dec 01, 2011 at 01:56:54PM +0000, Mark Brown wrote:
> For later chip revisions the WM1811 GPIO6 register is always volatile so
> store the device revision when initialising the driver and then check at
> runtime if we're running on a newer device.
This one depends on your regmap branch, so I'll let you push it.
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2011-12-19 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 13:56 [PATCH 1/2] mfd: Add missing mutex.h inclusion to WM8994 core.h Mark Brown
2011-12-01 13:56 ` [PATCH 2/2] mfd: Mark WM1811 GPIO6 register volatile for later revisions Mark Brown
2011-12-19 11:17 ` Samuel Ortiz [this message]
2011-12-19 11:18 ` [PATCH 1/2] mfd: Add missing mutex.h inclusion to WM8994 core.h 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=20111219111702.GC11800@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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 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.