From: Andrew Morton <akpm@osdl.org>
To: Len Brown <lenb@kernel.org>
Cc: Andi Kleen <ak@muc.de>, linux-acpi@vger.kernel.org
Subject: Re: x86_64-mm-always-use-physical-delivery-mode-on-8-cpus vs git-acpi
Date: Sun, 28 Jan 2007 22:38:16 -0800 [thread overview]
Message-ID: <20070128223816.3ee4574a.akpm@osdl.org> (raw)
In-Reply-To: <200701282158.12540.lenb@kernel.org>
On Sun, 28 Jan 2007 21:58:12 -0500
Len Brown <lenb@kernel.org> wrote:
> > OK, so I took another look. This ACPI update does extensive damage to
> > Andi's pending queue. I fixed four patches, dropped four or five more, hit
> > more problems then gave up again. I'll go back to Thursday's git-acpi
> > again.
> >
> > Longer-term, I expect Andi will merge before acpi does, and you're looking
> > at a fairly large amount of fixing after that happens.
>
> Exactly what patches from Andi do I need to merge on top of to get the ACPI tree into -mm?
ftp://ftp.firstfloor.org/pub/ak/x86_64/quilt/patches/ is everything.
In rc6-mm1 that's everything between #X86_64-START and #X86_64-END in the
series file. I have another 35-odd x86 patches on top of that lot.
Note that I normally stage the x86_64 tree _after_ the ACPI tree, but I can
change that.
I don't think that making the acpi tree dependent upon the x86_64 tree
would be a smart idea, frankly. It'll cause you heaps of pain.
Perhaps Andi could stick his tree into git for you to base off, dunno. But
he doesn't seem to be around at present.
prev parent reply other threads:[~2007-01-29 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 1:24 x86_64-mm-always-use-physical-delivery-mode-on-8-cpus vs git-acpi Andrew Morton
2007-01-27 9:29 ` Len Brown
2007-01-27 9:38 ` Andrew Morton
2007-01-27 22:20 ` Andrew Morton
2007-01-29 2:58 ` Len Brown
2007-01-29 6:38 ` Andrew Morton [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=20070128223816.3ee4574a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@muc.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.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