From: Miles Lane <miles.lane@comcast.net>
To: Gergely Nagy <algernon@bonehunter.rulez.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: [TRIVIAL] compile fix for arch/ppc/kernel/setup.c
Date: Sun, 3 Aug 2003 14:47:55 -0700 [thread overview]
Message-ID: <200308031447.55659.miles.lane@comcast.net> (raw)
In-Reply-To: <20030803204138.GB18494@gandalph.mad.hu>
On Sun August 3 2003 1:41 pm, Gergely Nagy wrote:
> Hi!
>
> I'm posting both to linuxppc-dev and lkml, since the latter is listed in
> MAINTAINERS. I've been trying to get my PowerMac 4400 boot with linux
> 2.6.0-test2(-bk3), but the compile failed quite early in
> arch/ppc/kernel/setup.c. After adding an #include <linux/cpu.h>, it
> compiled. Patch is included below.
>
> --- arch/ppc/kernel/setup.c.old 2003-08-03 22:35:51.000000000 +0200
> +++ arch/ppc/kernel/setup.c 2003-08-03 22:35:41.000000000 +0200
> @@ -2,6 +2,7 @@
> * Common prep/pmac/chrp boot and setup code.
> */
>
> +#include <linux/config.h>
> #include <linux/cpu.h>
> #include <linux/module.h>
> #include <linux/string.h>
>
>
> --
Hmm. This doesn't look like the correct patch. This one shows linux/config.h
being added, not linux/cpu.h. How about this one, instead?
--- arch/ppc/kernel/setup.c~ 2003-08-03 10:46:40.000000000 -0700
+++ arch/ppc/kernel/setup.c 2003-08-03 10:48:04.000000000 -0700
@@ -15,6 +15,7 @@
#include <linux/bootmem.h>
#include <linux/seq_file.h>
#include <linux/root_dev.h>
+#include <linux/cpu.h>
#include <asm/residual.h>
#include <asm/io.h>
next prev parent reply other threads:[~2003-08-03 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 20:41 [TRIVIAL] compile fix for arch/ppc/kernel/setup.c Gergely Nagy
2003-08-03 21:47 ` Miles Lane [this message]
2003-08-03 22:00 ` Gergely Nagy
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=200308031447.55659.miles.lane@comcast.net \
--to=miles.lane@comcast.net \
--cc=algernon@bonehunter.rulez.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).