From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: [PATCH 0/2] mfd: arizona: Updates for v3.8
Date: Tue, 20 Nov 2012 13:32:12 +0900 [thread overview]
Message-ID: <20121120043211.GE4483@opensource.wolfsonmicro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
The following changes since commit f4a75d2eb7b1e2206094b901be09adb31ba63681:
Linux 3.7-rc6 (2012-11-16 17:42:40 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/misc.git tags/mfd-arizona-3.8
for you to fetch changes up to ffe70f1e526c43b9bb56c9b4408b6e39d2b8473c:
mfd: wm5102: Mark some more status registers as volatile (2012-11-20 13:21:54 +0900)
----------------------------------------------------------------
mfd: arizona: Enhancements for v3.8
These have all previously been posted.
----------------------------------------------------------------
Mark Brown (2):
mfd: wm5102: Update maximum register
mfd: wm5102: Mark some more status registers as volatile
drivers/mfd/wm5102-tables.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-11-20 4:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 4:32 Mark Brown [this message]
2012-11-20 4:33 ` [PATCH 1/2] mfd: wm5102: Update maximum register Mark Brown
2012-11-20 4:33 ` [PATCH 2/2] mfd: wm5102: Mark some more status registers as volatile Mark Brown
2012-11-20 11:22 ` [PATCH 0/2] mfd: arizona: Updates for v3.8 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=20121120043211.GE4483@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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®