From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 13/23] regulator: ab3100: refactor probe to use IDs
Date: Mon, 22 Apr 2013 13:37:49 +0100 [thread overview]
Message-ID: <20130422123749.GJ30351@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1366624634-6579-1-git-send-email-linus.walleij@stericsson.com>
On Mon, Apr 22, 2013 at 11:57:14AM +0200, Linus Walleij wrote:
> Hi Mark, seeking an ACK on this to take it through the
> ARM SoC tree.
Since the arm-soc tree is locked down now I may as well just apply it so
it shows up in the merge window?
-------------- 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/20130422/ead68297/attachment.sig>
next prev parent reply other threads:[~2013-04-22 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 9:57 [PATCH 13/23] regulator: ab3100: refactor probe to use IDs Linus Walleij
2013-04-22 12:37 ` Mark Brown [this message]
2013-04-25 13:40 ` Linus Walleij
2013-04-24 9:54 ` Mark Brown
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=20130422123749.GJ30351@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).