From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: voltage tree build failure
Date: Mon, 12 Oct 2009 15:35:17 +0200 [thread overview]
Message-ID: <20091012133516.GA16662@sortiz.org> (raw)
In-Reply-To: <20091012125707.GE22233@sirena.org.uk>
On Mon, Oct 12, 2009 at 01:57:07PM +0100, Mark Brown wrote:
> On Sun, Oct 11, 2009 at 10:50:54PM -0400, Haojian Zhuang wrote:
>
> > Hi Samuel & Liam,
>
> > Please help review and merge this fix patch. I'm sorry for inconvience.
>
> This is waiting for Samuel - it should go via the MFD tree. I've CCed
> in Samuel's current e-mail address on the off-chance that that helps.
Patch applied and pushed. Sorry for the delay, I wasnt cc'ed at first.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2009-10-12 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 2:26 linux-next: voltage tree build failure Stephen Rothwell
2009-10-12 2:50 ` Haojian Zhuang
2009-10-12 2:50 ` Haojian Zhuang
2009-10-12 12:57 ` Mark Brown
2009-10-12 13:35 ` Samuel Ortiz [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-24 4:40 Stephen Rothwell
2009-08-24 9:51 ` Liam Girdwood
2009-04-28 6:24 Stephen Rothwell
2009-04-28 11:08 ` Liam Girdwood
2009-04-28 11:42 ` Stephen Rothwell
2009-04-30 11:06 ` Mike Rapoport
2009-01-21 2:46 Stephen Rothwell
2009-01-21 14:04 ` Jonathan Cameron
2008-07-14 13:35 Stephen Rothwell
2008-07-14 13:48 ` Liam Girdwood
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=20091012133516.GA16662@sortiz.org \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sfr@canb.auug.org.au \
/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.