From: Roland Dreier <rdreier@cisco.com>
To: vgoyal@in.ibm.com
Cc: linux-kernel@vger.kernel.org,
"Natalie.Protasevich@unisys.com" <Natalie.Protasevich@unisys.com>,
akpm@linux-foundation.org
Subject: Re: CONFIG_X86_ES7000=y, CONFIG_X86_GENERICARCH=n, CONFIG_ACPI=y build broken
Date: Wed, 13 Jun 2007 13:39:29 -0700 [thread overview]
Message-ID: <adamyz34mim.fsf@cisco.com> (raw)
In-Reply-To: <20070613173741.GA23618@in.ibm.com> (Vivek Goyal's message of "Wed, 13 Jun 2007 23:07:41 +0530")
> Can you please try the attached patch? I have compiled it with CONFIG_ES7000=y
> and CONFIG_X86_GENERICARCH=n. But don't have any ES7000 machine to test it.
I actually don't have anything remotely like ES7000 iether. I just
found the problem while tracking down another randconfig failure.
> Subarch build procedure is not straightforward and this patch adds to the
> misery. Please suggest if there is a better way of handling things.
> +/*
> + * This file also gets compiled if CONFIG_X86_GENERICARCH is set. Generic
> + * arch already has got following function definitions (asm-generic/es7000.c)
> + * hence no need to define these for that case.
> + */
> +#ifndef CONFIG_X86_GENERICARCH
Seems it would be cleaner to figure out some way to build es7000.c for
if CONFIG_X86_ES7000 is set? Or just move them here all the time?
> --- linux-2.6.22-rc4-git4/include/asm-i386/mach-es7000/mach_mpparse.h~i386-es7000-build-breakage-fix 2007-06-13 22:52:14.000000000 +0530
> +++ linux-2.6.22-rc4-git4-vivek/include/asm-i386/mach-es7000/mach_mpparse.h 2007-06-13 22:52:14.000000000 +0530
> @@ -18,6 +18,12 @@ extern int parse_unisys_oem (char *oempt
> extern int find_unisys_acpi_oem_table(unsigned long *oem_addr);
> extern void setup_unisys(void);
>
> +#ifndef CONFIG_X86_GENERICARCH
> +extern int acpi_madt_oem_check(char *oem_id, char *oem_table_id);
> +extern int mps_oem_check(struct mp_config_table *mpc, char *oem,
> + char *productid);
> +#endif
It seems that this #ifndef is not needed -- even if there is another
declaration of these functions that is visible, the signatures should
match so it should be OK.
- R.
next prev parent reply other threads:[~2007-06-13 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 19:13 Roland Dreier
2007-06-13 17:37 ` Vivek Goyal
2007-06-13 20:39 ` Roland Dreier [this message]
2007-06-15 15:57 ` Vivek Goyal
[not found] <19D0D50E9B1D0A40A9F0323DBFA04ACC023B0EB8@USRV-EXCH4.na.uis.unisys.com>
[not found] ` <32209efe0706131107w157fd59bk22f1fe62e4d1c733@mail.gmail.com>
2007-06-13 18:53 ` Natalie Protasevich
[not found] <19D0D50E9B1D0A40A9F0323DBFA04ACC023B0EB9@USRV-EXCH4.na.uis.unisys.com>
2007-06-13 22:22 ` Natalie Protasevich
2007-06-15 15:29 ` Vivek Goyal
2007-06-15 17:27 ` Natalie Protasevich
[not found] <19D0D50E9B1D0A40A9F0323DBFA04ACC023B0EBD@USRV-EXCH4.na.uis.unisys.com>
2007-06-17 14:34 ` Natalie Protasevich
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=adamyz34mim.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=Natalie.Protasevich@unisys.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
/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
Powered by JetHome