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/cleanups for v2.6.31
Date: Thu, 11 Jun 2009 00:07:37 +0200 [thread overview]
Message-ID: <20090610220737.GA11411@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.01.0906101500200.6847@localhost.localdomain>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, 10 Jun 2009, Ingo Molnar wrote:
>
> >
> > Please pull the latest x86-cleanups-for-linus git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-cleanups-for-linus
>
> Just checking - these are all independent and it doesn't much
> matter which order I pull in, right?
Yes - each is -git based and independent. To make sure i also built
each one before sending, and also booted the ones i wanted to
double-check (about half of them).
> That way I can go through the easy ones first, which helps me get
> around to the ones I decide I want to think about more later.
Yeah. Any order should be fine and if there are conflicts they
should be straightforward.
Any unreasonably heavy conflict was resolved by merging topics into
a single entity. This happened for one of the branches: the IRQ bits
i sent started out as x86/apic - the the scope of the changes
increased on the way.
No unreasonable mixing of topics happened in this cycle - the topic
separation worked out fine, due to increased attention we spent on
making it happen and due to the unification activities winding down
(finally! :-).
Ingo
prev parent reply other threads:[~2009-06-10 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 21:12 [GIT PULL] x86/cleanups for v2.6.31 Ingo Molnar
2009-06-10 22:01 ` Linus Torvalds
2009-06-10 22:07 ` 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=20090610220737.GA11411@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