public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-mm2
Date: Tue, 8 Mar 2005 15:58:36 +0200	[thread overview]
Message-ID: <20050308135836.GC12820@linux-sh.org> (raw)
In-Reply-To: <20050308033846.0c4f8245.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]

With the BUG_ON() use in linux/list.h I get this:

  CC      init/initramfs.o
In file included from include/linux/wait.h:23,
                 from include/linux/fs.h:205,
                 from init/initramfs.c:2:
include/linux/list.h: In function `list_del':
include/linux/list.h:164: warning: implicit declaration of function `printk'
In file included from include/linux/spinlock.h:13,
                 from include/linux/wait.h:25,
                 from include/linux/fs.h:205,
                 from init/initramfs.c:2:
include/linux/kernel.h: At top level:
include/linux/kernel.h:116: error: conflicting types for 'printk'
include/linux/kernel.h:116: note: a parameter list with an ellipsis can't match an empty parameter name list declaration
include/linux/list.h:164: error: previous implicit declaration of 'printk' was here
make[1]: *** [init/initramfs.o] Error 1
make: *** [init] Error 2

It looks like this is a result of having asm/bug.h included and not
having linux/kernel.h included before it, as adding that makes this go
away. This seems like it will be a problem for platforms that use
printk() in their BUG() definitions (in the HAVE_ARCH_BUG case) without
dragging in this header from somewhere else.

With this I can build on sh again. The other solution is to add the
include to asm/bug.h directly, but it would be nice to avoid linux/
includes from asm/ context in general..

Thoughts? Or ideas for a more appropriate fix?

--- linux-sh-2.6.11-mm2.orig/include/linux/list.h	2005-03-08 15:46:50.601565604 +0200
+++ linux-sh-2.6.11-mm2/include/linux/list.h	2005-03-08 15:46:53.882114403 +0200
@@ -5,6 +5,7 @@
 
 #include <linux/stddef.h>
 #include <linux/prefetch.h>
+#include <linux/kernel.h>
 #include <asm/system.h>
 #include <asm/bug.h>
 

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-08 13:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 11:38 2.6.11-mm2 Andrew Morton
2005-03-08 13:58 ` Paul Mundt [this message]
2005-03-08 19:40   ` 2.6.11-mm2 Andrew Morton
2005-03-08 16:00 ` 2.6.11-mm2 (compile stats) John Cherry
2005-03-08 18:54 ` 2.6.11-mm2 fremap.c compile error Jurriaan
2005-03-11 22:50   ` Adrian Bunk
2005-03-08 19:29 ` inconsistent kallsyms data [2.6.11-mm2] Dominik Brodowski
2005-03-08 20:35   ` Andrew Morton
2005-03-08 20:45     ` Dominik Brodowski
2005-03-09 12:57       ` Paulo Marques
2005-03-09 20:16         ` Paulo Marques
2005-03-10 12:12           ` Paulo Marques
2005-03-13  8:54             ` Sam Ravnborg
2005-03-14 13:33               ` Paulo Marques
2005-03-14 22:17               ` Dominik Brodowski
2005-03-14 22:14             ` Dominik Brodowski
2005-03-08 23:20 ` 2.6.11-mm2 Christoph Hellwig
2005-03-08 23:29   ` 2.6.11-mm2 Andrew Morton
2005-03-08 23:36 ` 2.6.11-mm2 J.A. Magallon
2005-03-08 23:44   ` 2.6.11-mm2 Robert Love
2005-03-08 23:51     ` 2.6.11-mm2 J.A. Magallon
2005-03-09  0:02       ` 2.6.11-mm2 Robert Love
2005-03-09  0:16 ` 2.6.11-mm2 Adrian Bunk
2005-03-09  0:53   ` 2.6.11-mm2 Andrew Morton
2005-03-09  1:39     ` 2.6.11-mm2 Jeff Garzik
2005-03-09  0:20 ` 2.6.11-mm2 Adrian Bunk
2005-03-09  1:50   ` 2.6.11-mm2 Karsten Keil
2005-03-10  7:57 ` 2.6.11-mm2 Stefano Rivoir
2005-03-10  8:09   ` 2.6.11-mm2 Andrew Morton
2005-03-21 23:45   ` 2.6.11-mm2 Andrew Morton

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=20050308135836.GC12820@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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