From: Samuel Ortiz <sameo@openedhand.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] WM8350 updates
Date: Tue, 21 Oct 2008 00:44:35 +0200 [thread overview]
Message-ID: <20081020224435.GE4197@sortiz.org> (raw)
In-Reply-To: <20081020190022.GA9504@rakim.wolfsonmicro.main>
Hi Mark,
On Mon, Oct 20, 2008 at 08:00:22PM +0100, Mark Brown wrote:
> A couple of minor WM8350 updates here. The first, from Stephen
> Rothwell needs to be merged with Linus fairly urgently. The second
> is less urgent since nothing merged should be affected, though it should
> still be safe to merge.
Both of them merged to my mfd-next tree. I'll send a pull request to Linus
tomorrow.
Thanks for the patches.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2008-10-20 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 19:00 [PATCH 0/2] WM8350 updates Mark Brown
2008-10-20 19:01 ` [PATCH 1/2] mfd/wm8350: don't export static functions Mark Brown
2008-10-20 19:01 ` [PATCH 2/2] mfd: Don't store volatile bits in WM8350 register cache Mark Brown
2008-10-20 22:44 ` Samuel Ortiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-05 18:12 [PATCH 0/2] WM8350 updates Mark Brown
2009-02-06 14:10 ` 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=20081020224435.GE4197@sortiz.org \
--to=sameo@openedhand.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.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