From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/cpufeature for v2.6.31
Date: Thu, 11 Jun 2009 01:00:56 +0200 [thread overview]
Message-ID: <20090610230056.GA13641@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.01.0906101554320.6847@localhost.localdomain>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Wed, 10 Jun 2009, Ingo Molnar wrote:
> >
> > Please pull the latest x86-cpufeature-for-linus git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-cpufeature-for-linus
>
> Hmm. This was already part of the irq-tree.
Ah, sorry - due to:
commit ee4c24a5c9b530481394132c8dbc10572d57c075
Merge: 3d58f48... 3e0c373...
Author: Ingo Molnar <mingo@elte.hu>
Date: Mon Jun 1 22:29:35 2009 +0200
Merge branch 'x86/cpufeature' into irq/numa
Merge reason: irq/numa didnt build because this commit:
2759c32: x86: don't call read_apic_id if !cpu_has_apic
Had a dependency on x86/cpufeature changes. Pull in that
(small) branch to fix the dependency.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
This seemed like one of the exceptions to do that merge -
x86/cpufeature is a narrow 'infrastructure' topic we keep around
during the development window, because we found it in the past that
cpufeature changes frequently cause conflicts and merge
dependencies. The cpufeatres commits are always kept uninteresting
and non-controversial.
So technically it's a cross-tree merge, but of the good and
exceptional kind ... i hope :-/
> (But at least so far, this merge window looks much cleaner wrt x86
> merges.
Thanks :)
> [...] I'm hoping there are no nasty surprises down the line ;)
There are none planned! :-)
Ingo
prev parent reply other threads:[~2009-06-10 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 21:16 [GIT PULL] x86/cpufeature for v2.6.31 Ingo Molnar
2009-06-10 22:54 ` Linus Torvalds
2009-06-10 23:00 ` Ingo Molnar [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=20090610230056.GA13641@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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