From: Joerg Roedel <joerg.roedel@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: x86 tree build failure
Date: Fri, 12 Sep 2008 08:05:27 +0200 [thread overview]
Message-ID: <20080912060527.GA22003@amd.com> (raw)
In-Reply-To: <20080912095618.728658a5.sfr@canb.auug.org.au>
Hi Stephen,
do you have these commits in next/master already? I tried to find out
why it fails (the build failure is weird because
PCI_DEVICE_ID_AMD_10H_NB_MISC and PCI_DEVICE_ID_AMD_11H_NB_MISC
are defined in the same place in tip/master).
Joerg
On Fri, Sep 12, 2008 at 09:56:18AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> arch/x86/kernel/k8.c:20: error: 'PCI_DEVICE_ID_AMD_10H_NB_MISC' undeclared here (not in a function)
>
> Introduced by commit cf169702ba6928cee9d4f4adf3e932b643b8db7a ("x86,
> gart: add detection of AMD family 0x11 northbridges"). I applied the
> following patch.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri, 12 Sep 2008 09:52:19 +1000
> Subject: [PATCH] x86: fix arch/x86/kernel/k8.c
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> arch/x86/kernel/k8.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kernel/k8.c b/arch/x86/kernel/k8.c
> index 304d8ba..3f5b832 100644
> --- a/arch/x86/kernel/k8.c
> +++ b/arch/x86/kernel/k8.c
> @@ -17,7 +17,7 @@ static u32 *flush_words;
>
> struct pci_device_id k8_nb_ids[] = {
> { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_K8_NB_MISC) },
> - { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_10H_NB_MISC) },
> + { PCI_DEVICE(PCI_VENDOR_ID_AMD, 0x1203) },
> { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_11H_NB_MISC) },
> {}
> };
> --
> 1.5.6.3
>
>
--
| AMD Saxony Limited Liability Company & Co. KG
Operating | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
System | Register Court Dresden: HRA 4896
Research | General Partner authorized to represent:
Center | AMD Saxony LLC (Wilmington, Delaware, US)
| General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-09-12 6:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 23:56 linux-next: x86 tree build failure Stephen Rothwell
2008-09-12 6:05 ` Joerg Roedel [this message]
2008-09-12 7:31 ` Stephen Rothwell
2008-09-12 7:54 ` Joerg Roedel
2008-09-12 8:30 ` Ingo Molnar
2008-09-14 19:52 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-08-25 10:22 Stephen Rothwell
2008-08-25 10:28 ` Ingo Molnar
2008-07-17 2:07 Stephen Rothwell
2008-07-17 9:23 ` Vegard Nossum
2008-07-18 20:10 ` Ingo Molnar
2008-07-18 20:12 ` Ingo Molnar
2008-07-19 12:11 ` Stephen Rothwell
2008-06-17 3:46 Stephen Rothwell
2008-06-17 5:58 ` Ingo Molnar
2008-06-17 6:08 ` Ingo Molnar
2008-06-17 6:45 ` Ingo Molnar
2008-06-18 5:04 ` Stephen Rothwell
2008-06-18 6:39 ` Ingo Molnar
2008-06-25 3:17 ` Stephen Rothwell
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=20080912060527.GA22003@amd.com \
--to=joerg.roedel@amd.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).