public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource•wolfsonmicro.com>
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,
	Yong Shen <yong.shen@linaro•org>
Subject: Re: linux-next: build failure after merge of the voltage tree
Date: Wed, 15 Dec 2010 14:03:45 +0000	[thread overview]
Message-ID: <20101215140344.GF5723@sirena.org.uk> (raw)
In-Reply-To: <1292403884.3348.6.camel@odin>

On Wed, Dec 15, 2010 at 09:04:44AM +0000, Liam Girdwood wrote:

> Yong, can you send a patch *today* that fixes the modular build for
> this.

Looks like he's not going to get a chance to do that, I'm cooking up
some patches just now which should deal with the issue.

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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15  2:09 linux-next: build failure after merge of the voltage tree Stephen Rothwell
2010-12-15  9:04 ` Liam Girdwood
2010-12-15 14:03   ` Mark Brown [this message]
2010-12-15 14:10     ` [PATCH] regulator: Allow modular build of mc13xxx-core Mark Brown
2010-12-15 21:30       ` Liam Girdwood
2010-12-16  1:52         ` Yong Shen
  -- strict thread matches above, loose matches on Subject: below --
2011-05-10  2:44 linux-next: build failure after merge of the voltage tree 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-14  4:49 Stephen Rothwell
2010-12-14  5:10 ` Yong Shen
2010-12-14 15:56   ` Liam Girdwood
2010-12-15  2:03     ` Yong Shen
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=20101215140344.GF5723@sirena.org.uk \
    --to=broonie@opensource$(echo .)wolfsonmicro.com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=lrg@slimlogic$(echo .)co.uk \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=yong.shen@linaro$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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