All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <mike@compulab.co.il>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>, linux-next@vger.kernel.org
Subject: Re: linux-next: voltage tree build failure
Date: Thu, 30 Apr 2009 14:06:34 +0300	[thread overview]
Message-ID: <49F9863A.6010306@compulab.co.il> (raw)
In-Reply-To: <20090428214207.4a27d391.sfr@canb.auug.org.au>



Stephen Rothwell wrote:
> Hi Liam,
> 
> On Tue, 28 Apr 2009 12:08:37 +0100 Liam Girdwood <lrg@slimlogic.co.uk> wrote:
>> On Tue, 2009-04-28 at 16:24 +1000, Stephen Rothwell wrote:
>>> Hi Liam,
>>>
>>> Today's linux-next build (powerpc allyesconfig) failed like this:
>>>
>>> drivers/regulator/userspace-consumer.c:43: error: conflicting types for 'show_state'
>>> include/linux/sched.h:273: note: previous definition of 'show_state' was here
>>>
>>> Caused by commit 5defa2bce704ca4151cfe24e4297aa7797cafd22 ("regulator:
>>> add userspace-consumer driver") which I have reverted for today.
>> Sorry about this. I've now fixed in voltage next by renaming with a reg_
>> prefix. Fwiw - I did test build for ARM and all was OK yesterday. I
>> guess I need to build allyesconfig too.

It's rather my fault...
BTW, the drivers/regulator/virtual.c has show_mode which may trigger similar
error later, probably it's worth adding reg_ prefix there as well...

> More likely, sched.h is indirectly included on some platforms and not
> others.  This is partly what linux-next is for: to find cross platform
> and subsystem interactions.
> 
> Thanks for the fix.

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2009-04-30 11:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  6:24 linux-next: voltage tree build failure Stephen Rothwell
2009-04-28 11:08 ` Liam Girdwood
2009-04-28 11:42   ` Stephen Rothwell
2009-04-30 11:06     ` Mike Rapoport [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-12  2:26 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
2009-08-24  4:40 Stephen Rothwell
2009-08-24  9:51 ` Liam Girdwood
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=49F9863A.6010306@compulab.co.il \
    --to=mike@compulab.co.il \
    --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.