From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: x86 tree build failure
Date: Fri, 12 Sep 2008 10:30:23 +0200 [thread overview]
Message-ID: <20080912083023.GA1082@elte.hu> (raw)
In-Reply-To: <20080912173141.5b268bed.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Joerg,
>
> On Fri, 12 Sep 2008 08:05:27 +0200 Joerg Roedel <joerg.roedel@amd.com> wrote:
> >
> > do you have these commits in next/master already? I tried to find out
>
> Not until tomorrow some time, sorry.
>
> > 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).
>
> tip/master has more trees merged than the x86 tree (and indeed
> PCI_DEVICE_ID_AMD_10H_NB_MISC turns up in the timers tree).
hm, but linux-next should have the timers tree merged too. So how come
you triggered this build error?
Ingo
next prev parent reply other threads:[~2008-09-12 8:30 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
2008-09-12 7:31 ` Stephen Rothwell
2008-09-12 7:54 ` Joerg Roedel
2008-09-12 8:30 ` Ingo Molnar [this message]
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=20080912083023.GA1082@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=joerg.roedel@amd.com \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.