public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Rui Sousa <rui.p.m.sousa@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ingo Molnar <mingo@elte.hu>, linux-next@vger.kernel.org
Subject: Re: linux-next: tip-core build failure
Date: Sat, 13 Sep 2008 11:44:35 +0200	[thread overview]
Message-ID: <200809131144.36507.rui.p.m.sousa@gmail.com> (raw)
In-Reply-To: <20080913111423.981554c3.sfr@canb.auug.org.au>

On Saturday 13 September 2008 03:14, Stephen Rothwell wrote:
> Hi Ingo,
>
> Today's linux-next build (powerpc allnoconfig) failed like this:
>
> In file included from arch/powerpc/include/asm/system.h:8,
>                  from include/linux/list.h:7,
>                  from include/linux/signal.h:8,
>                  from arch/powerpc/kernel/asm-offsets.c:16:
> include/linux/irqflags.h:89:1: warning: "local_irq_save" redefined
> In file included from arch/powerpc/include/asm/irqflags.h:11,
>                  from include/linux/irqflags.h:55,
>                  from arch/powerpc/include/asm/system.h:8,
>                  from include/linux/list.h:7,
>                  from include/linux/signal.h:8,
>                  from arch/powerpc/kernel/asm-offsets.c:16:
> arch/powerpc/include/asm/hw_irq.h:115:1: warning: this is the location of
> the previous definition
>
> And it went downhill from there.
>
> Introduced by commit bd8fbdee6562ee526f3c2582a3b373ef195015dd ("lockdep:
> fix compilation when CONFIG_TRACE_IRQFLAGS_SUPPORT is not set") which I
> have reverted.

Ingo,

Do you agree that the original (in include/linux/irqflags.h):

#define raw_local_irq_disable()        local_irq_disable()

should be

#define local_irq_disable()		raw_local_irq_disable()        

and that architecture specific files should only define the raw_xxx() macros?
It seems I missed a bunch of need changes in the original patch, but if it's
the right way to go I can work on a patch to update the other archs too.

Thanks,
Rui

  reply	other threads:[~2008-09-13  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-13  1:14 linux-next: tip-core build failure Stephen Rothwell
2008-09-13  9:44 ` Rui Sousa [this message]
2008-09-14 12:43   ` Ingo Molnar
2008-09-14 18:01     ` Stephen Rothwell
2008-09-14 18:36       ` Ingo Molnar
2008-09-14 19:02         ` Stephen Rothwell
2008-09-14 19:17           ` Ingo Molnar
2008-09-14 19:45             ` Stephen Rothwell
2008-09-15  8:11               ` Ingo Molnar
2008-09-15 13:02                 ` Rui Sousa

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=200809131144.36507.rui.p.m.sousa@gmail.com \
    --to=rui.p.m.sousa@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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