linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yong Shen <yong.shen@linaro.org>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the voltage tree
Date: Wed, 15 Dec 2010 10:03:10 +0800	[thread overview]
Message-ID: <AANLkTikAvw2_jXUynFshnturwe6jF5N3+4-fUpgEhS+F@mail.gmail.com> (raw)
In-Reply-To: <1292342215.3316.17.camel@odin>

Hi Liam,

Thanks for reminding. I will bear that in mind.

Thanks
Yong

On Tue, Dec 14, 2010 at 11:56 PM, Liam Girdwood <lrg@slimlogic.co.uk> wrote:
> On Tue, 2010-12-14 at 13:10 +0800, Yong Shen wrote:
>> Hi Stephen,
>>
>> I had already noticed Liam. Mc13892's patch depends on other two
>> patches which are not applied yet.
>>
>
> All applied now.
>
> Yong, in the future please wait until patches are applied before sending
> new dependent patches. This series and the last were quite confusing to
> deal with due to the sheer number of similar subject emails.
>
> Thanks
>
> Liam
> --
> Freelance Developer, SlimLogic Ltd
> ASoC and Voltage Regulator Maintainer.
> http://www.slimlogic.co.uk
>
>

  reply	other threads:[~2010-12-15  2:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14  4:49 linux-next: build failure after merge of the voltage tree Stephen Rothwell
2010-12-14  5:10 ` Yong Shen
2010-12-14 15:56   ` Liam Girdwood
2010-12-15  2:03     ` Yong Shen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-10  2:44 Stephen Rothwell
2011-05-10  8:38 ` Liam Girdwood
2011-05-10 17:30   ` Jorge Eduardo Candelaria
2011-05-10 19:57     ` Liam Girdwood
2011-05-11  2:27     ` Stephen Rothwell
2011-05-11  6:43       ` Jorge Eduardo Candelaria
2011-05-11 13:29         ` Liam Girdwood
2010-12-15  2:09 Stephen Rothwell
2010-12-15  9:04 ` Liam Girdwood
2010-12-15 14:03   ` Mark Brown
2010-11-11  0:36 Stephen Rothwell
2010-11-11 11:46 ` Mark Brown
2010-11-11 12:09   ` 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=AANLkTikAvw2_jXUynFshnturwe6jF5N3+4-fUpgEhS+F@mail.gmail.com \
    --to=yong.shen@linaro.org \
    --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 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).