All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Liam Girdwood <lrg@ti.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Randy Dunlap <rdunlap@xenotime.net>,
	akpm <akpm@linux-foundation.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] regulator: aat2870-regulator.c needs module.h
Date: Wed, 3 Aug 2011 12:28:52 +0200	[thread overview]
Message-ID: <20110803102852.GD26275@sortiz-mobl> (raw)
In-Reply-To: <1312222186.5170.8.camel@CNA0741383>

Hi Liam,

On Mon, Aug 01, 2011 at 07:09:46PM +0100, Liam Girdwood wrote:
> Hi Samuel,
> 
> On Mon, 2011-08-01 at 11:25 +0200, Samuel Ortiz wrote:
> > Hi Stephen, Liam,
> > 
> > On Mon, Aug 01, 2011 at 11:05:07AM +1000, Stephen Rothwell wrote:
> > > On Mon, 1 Aug 2011 10:33:04 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > >
> > > > On Mon, 1 Aug 2011 01:15:24 +0100 Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> > > > >
> > > > > On Fri, Jul 29, 2011 at 09:13:09PM -0700, Randy Dunlap wrote:
> > > > > > From: Randy Dunlap <rdunlap@xenotime.net>
> > > > > > 
> > > > > > aat2870-regulator.c needs to include linux/module.h to fix multiple
> > > > > > build errors.
> > > > > 
> > > > > Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > > > > 
> > > > > but if the breakage isn't in mainline yet to minimize the breaks
> > > > > bisection someone should figure out which tree introduced the change
> > > > > with module.h and either get the fix merged along with that.  If neither
> > > > > the module.h change nor the driver is in Linus' tree yet I rather
> > > > > suspect this should go via MFD as I seem to recall that the driver is
> > > > > going in via there.
> > > > 
> > > > It is indeed.  I have this patch set to apply to my tree today after the
> > > > mfd tree.  Hopefully Samuel will put it in his tree for tomorrow (and
> > > > before he asks Linus to pull.
> > > 
> > > Too late :-)
> > Sorry about that. I thought I would hear about any breakage after I pushed my
> > bits on Friday morning.
> > Anyway, Liam, are you going to push this fix through your tree ?
> > 
> 
> I can if required, however I've just done my pull request (sorry didn't
> see this in time). I have to do another pull request with misc fixes in
> rc1 time frame so I can add it there if OK. 
That's fine with me, thanks in advance.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2011-08-03 10:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29  7:38 linux-next: Tree for July 29 Stephen Rothwell
2011-07-29 19:07 ` [PATCH -next] x86: files need export.h Randy Dunlap
2011-07-30 18:51   ` Paul Gortmaker
2011-07-29 19:43 ` [PATCH -next] regulator: aat2870 needs module.h Randy Dunlap
2011-07-30  1:04 ` [PATCH -next] x86: devicetree.h needs export.h Randy Dunlap
2011-07-30 19:00   ` Paul Gortmaker
2011-07-30  1:09 ` [PATCH -next] sfi: sfi_acpi.c needs sysfs.h Randy Dunlap
2011-07-30 19:05   ` Paul Gortmaker
2011-07-30  4:11 ` [PATCH -next] power: max8998_charger.c needs module.h Randy Dunlap
2011-08-19 17:02   ` Anton Vorontsov
2011-07-30  4:13 ` [PATCH -next] regulator: aat2870-regulator.c " Randy Dunlap
2011-08-01  0:15   ` Mark Brown
2011-08-01  0:33     ` Stephen Rothwell
2011-08-01  1:05       ` Stephen Rothwell
2011-08-01  9:25         ` Samuel Ortiz
2011-08-01  9:25           ` Samuel Ortiz
2011-08-01 18:09           ` Liam Girdwood
2011-08-03 10:28             ` Samuel Ortiz [this message]
2011-07-30  4:14 ` [PATCH -next] sound: rtctimer.c " Randy Dunlap
2011-07-30  6:04   ` Takashi Iwai
2011-07-30  4:14 ` [PATCH -next] i2c: i2c-pxa-pci.c " Randy Dunlap
     [not found]   ` <20110729211430.6c4830bd.rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-07-30 19:09     ` Paul Gortmaker
2011-07-30 19:09       ` Paul Gortmaker
2011-07-31 16:42       ` Ben Dooks
     [not found]         ` <20110731164208.GP15795-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-07-31 19:41           ` Paul Gortmaker
2011-07-31 19:41             ` Paul Gortmaker
2011-07-30  4:14 ` [PATCH -next] input: mouse/hgpk.c " Randy Dunlap
2011-07-30 19:02   ` Dmitry Torokhov
2011-07-30  4:14 ` [PATCH -next] x86/platform: geode/alix.c " Randy Dunlap
2011-07-30  4:14 ` [PATCH -next] x86/platform: mrst/pmu.c " Randy Dunlap
2011-07-30  4:14 ` Randy Dunlap
2011-08-01 15:31   ` Len Brown
2011-08-01 15:31   ` Len Brown
2011-07-30 11:38 ` linux-next: Tree for July 29 Sedat Dilek
2011-07-30 16:08   ` Arnaud Lacombe
2011-07-30 16:16     ` Sedat Dilek

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=20110803102852.GD26275@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=rdunlap@xenotime.net \
    --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.