From: Greg Ungerer <gerg@snapgear.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: gerg@uclinux.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] arch/m68knommu/kernel/setup.c should always #include <asm/pgtable.h>
Date: Mon, 11 Sep 2006 15:01:32 +1000 [thread overview]
Message-ID: <4504EDAC.9050900@snapgear.com> (raw)
In-Reply-To: <20060904221158.GA9173@stusta.de>
Hi Adrian,
Adrian Bunk wrote:
> This patch fixes the following compile error with
> CONFIG_BLK_DEV_INITRD=n and -Werror-implicit-function-declaration:
>
> <-- snip -->
>
> ...
> CC arch/m68knommu/kernel/setup.o
> /home/bunk/linux/kernel-2.6/linux-2.6.18-rc5-mm1/arch/m68knommu/kernel/setup.c: In function 'setup_arch':
> /home/bunk/linux/kernel-2.6/linux-2.6.18-rc5-mm1/arch/m68knommu/kernel/setup.c:268: error: implicit declaration of function 'paging_init'
> make[2]: *** [arch/m68knommu/kernel/setup.o] Error 1
>
> <-- snip -->
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Thanks, I'll push that.
Regards
Greg
> --- linux-2.6.18-rc5-mm1/arch/m68knommu/kernel/setup.c.old 2006-09-05 00:07:42.000000000 +0200
> +++ linux-2.6.18-rc5-mm1/arch/m68knommu/kernel/setup.c 2006-09-05 00:08:20.000000000 +0200
> @@ -36,10 +36,7 @@
> #include <asm/setup.h>
> #include <asm/irq.h>
> #include <asm/machdep.h>
> -
> -#ifdef CONFIG_BLK_DEV_INITRD
> #include <asm/pgtable.h>
> -#endif
>
> unsigned long memory_start;
> unsigned long memory_end;
>
>
--
------------------------------------------------------------------------
Greg Ungerer -- Chief Software Dude EMAIL: gerg@snapgear.com
SnapGear -- a Secure Computing Company PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2006-09-11 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 22:11 [2.6 patch] arch/m68knommu/kernel/setup.c should always #include <asm/pgtable.h> Adrian Bunk
2006-09-11 5:01 ` Greg Ungerer [this message]
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=4504EDAC.9050900@snapgear.com \
--to=gerg@snapgear.com \
--cc=bunk@stusta.de \
--cc=gerg@uclinux.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