From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4 V5] add 88pm80x mfd driver
Date: Mon, 9 Jul 2012 11:55:33 +0100 [thread overview]
Message-ID: <20120709105533.GA3934@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120709105551.GK15345@sortiz-mobl>
On Mon, Jul 09, 2012 at 12:55:51PM +0200, Samuel Ortiz wrote:
> I applied the first 2 patches, I'd like to get an ACK from the respective
> maintainers for the rtc and the input ones. They can even take it as both
> drivers are protected by the MFD symbol.
Alessandro's been mostly offline recently so it might be as well to
apply the RTC patch anyway.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120709/50663325/attachment.sig>
next prev parent reply other threads:[~2012-07-09 10:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 6:37 [PATCH 0/4 V5] add 88pm80x mfd driver Qiao Zhou
2012-07-09 6:37 ` [PATCH 1/4 V5] mfd: support 88pm80x in 80x driver Qiao Zhou
2012-07-09 6:37 ` [PATCH 2/4 V5] mfd: workaround: add companion chip in 88pm80x Qiao Zhou
2012-07-09 6:37 ` [PATCH 3/4 V5] rtc: add rtc support to 88PM80X PMIC Qiao Zhou
2012-07-09 6:37 ` [PATCH 4/4 V5] input: add onkey " Qiao Zhou
2012-07-09 10:55 ` [PATCH 0/4 V5] add 88pm80x mfd driver Samuel Ortiz
2012-07-09 10:55 ` Mark Brown [this message]
2012-07-09 13:21 ` Samuel Ortiz
2012-07-09 14:48 ` Qiao Zhou
2012-07-09 11:46 ` Arnd Bergmann
2012-07-09 13:14 ` Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2012-07-09 14:57 Qiao Zhou
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=20120709105533.GA3934@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).