From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
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: Wed, 10 Jun 2009 15:54:41 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906101554320.6847@localhost.localdomain> (raw)
In-Reply-To: <20090610211629.GA11105@elte.hu>
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.
(But at least so far, this merge window looks much cleaner wrt x86 merges.
I'm hoping there are no nasty surprises down the line ;)
Linus
next prev parent reply other threads:[~2009-06-10 22:55 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 [this message]
2009-06-10 23:00 ` Ingo Molnar
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=alpine.LFD.2.01.0906101554320.6847@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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