public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: Build breakage ...
Date: Mon, 27 Nov 2006 00:08:45 +0000	[thread overview]
Message-ID: <20061127000845.GA23899@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0611261459010.3483@woody.osdl.org>

On Sun, Nov 26, 2006 at 03:06:10PM -0800, Linus Torvalds wrote:

> That said, Alexey did check it more than most patches like this get 
> checked (ie checking allmodconfig on i386, x86_64, alpha, arm), so it's a 
> bit unlucky that MIPS got bitten by this - it was not a badly tested 
> patch per se.
> 
> Does the obvious fix (to include <linux/kernel.h> in irqflags.h) fix it 
> for you?

It changes the sympthoms:

  CC      arch/mips/kernel/asm-offsets.s
In file included from include/linux/irqflags.h:14,
                 from include/asm/bitops.h:34,
                 from include/linux/bitops.h:9,
                 from include/linux/thread_info.h:20,
                 from include/linux/preempt.h:9,
                 from include/linux/spinlock.h:49,
                 from include/linux/capability.h:45,
                 from include/linux/sched.h:46,
                 from arch/mips/kernel/asm-offsets.c:13:
include/linux/kernel.h: In function ‘roundup_pow_of_two’:
include/linux/kernel.h:169: warning: implicit declaration of function ‘fls_long’
In file included from include/linux/thread_info.h:20,
                 from include/linux/preempt.h:9,
                 from include/linux/spinlock.h:49,
                 from include/linux/capability.h:45,
                 from include/linux/sched.h:46,
                 from arch/mips/kernel/asm-offsets.c:13:
include/linux/bitops.h: At top level:
include/linux/bitops.h:57: error: conflicting types for ‘fls_long’
include/linux/kernel.h:169: error: previous implicit declaration of ‘fls_long’ was here

So the new problem is circular includes:

   ... <linux/bitops.h> -> <asm/bitops.h> -> <linux/irqflags.h> ->
  <linux/kernel.h> -> <linux/bitops.h> ...

include/asm-mips/bitops.h needs to include irqflags because some older
MIPS variants do not have any atomic instructions.  So the fix needs to
to break that loop.

  Ralf

  parent reply	other threads:[~2006-11-27  0:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 22:49 Build breakage Ralf Baechle
2006-11-26 23:05 ` Russell King
2006-11-26 23:09   ` Russell King
2006-11-26 23:06 ` Linus Torvalds
2006-11-26 23:12   ` Linus Torvalds
2006-11-26 23:21     ` Russell King
2006-11-27  0:29       ` Linus Torvalds
2006-11-27  0:41         ` Russell King
2006-11-27 16:43         ` Ralf Baechle
2006-11-27 19:56           ` Alexey Dobriyan
2006-11-27  0:08   ` Ralf Baechle [this message]
2006-11-26 23:47 ` Kyle McMartin
2006-11-26 23:56   ` [PARISC] Fix incorrent type of flags in <asm/semaphore.h> Kyle McMartin

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=20061127000845.GA23899@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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