linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, Bob Moore <robert.moore@intel.com>,
	Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: linux-next: manual merge of the acpi tree
Date: Wed, 25 Jun 2008 15:18:40 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806251516460.3014@localhost.localdomain> (raw)
In-Reply-To: <20080625162923.GB6040@elte.hu>



On Wed, 25 Jun 2008, Ingo Molnar wrote:

> 
> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > On Wed, 25 Jun 2008 09:15:08 +0200 Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > I suspect we cannot really eliminate this particular conflict 
> > > because the latter change is a (much welcome!) infrastructure 
> > > cleanup in all things ACPI, the former is an early init 
> > > refactoring/cleanup that depends on a whole lot of other (non-ACPI) 
> > > changes in tip/x86/*. It's too late in .26-rc cycle to push the 
> > > infrastructure cleanup upstream, so i suspect we have to live with 
> > > this conflict for a while.
> > 
> > No problem.  How long can it be until all this is merged in Linus' 
> > tree anyway? :-)
> 
> if Len acks these patches i can do a by-line mini-topic with just these 
> commits and put them into tip/auto-x86-next. It's Len's call though :-)

Ingo,
can you point me tot he patches you'd like me to review/ack?

I don't understand how you propose to void a linux-next merge conflict --
unless you're going to cherry-pick the ACPICA changes into your tree?

thanks,
-Len

  reply	other threads:[~2008-06-25 19:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  4:20 linux-next: manual merge of the acpi tree Stephen Rothwell
2008-06-25  7:15 ` Ingo Molnar
2008-06-25 15:59   ` Stephen Rothwell
2008-06-25 16:29     ` Ingo Molnar
2008-06-25 19:18       ` Len Brown [this message]
2008-06-25 19:57         ` Ingo Molnar
2008-06-26 22:42           ` Len Brown
2008-06-27  7:17             ` Ingo Molnar
2008-06-25 14:24 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-12-01  2:10 Stephen Rothwell
2008-12-01  2:55 ` Len Brown
2008-12-01  3:02   ` Stephen Rothwell
2008-12-01  4:11     ` Len Brown
2008-12-01  4:37       ` Stephen Rothwell
2008-10-21  2:55 Stephen Rothwell
2008-10-20  4:45 Stephen Rothwell
2008-10-15  4:23 Stephen Rothwell
2008-10-15 16:10 ` Bjorn Helgaas
2008-10-15  4:14 Stephen Rothwell
2008-08-25  5:48 Stephen Rothwell
2008-07-17  4:22 Stephen Rothwell
2008-07-17  7:24 ` Adrian Bunk
2008-07-18  0:37   ` Stephen Rothwell
2008-07-17  4:05 Stephen Rothwell
2008-07-17  4:00 Stephen Rothwell
2008-07-17  4:29 ` Stephen Rothwell
2008-07-16  5:33 Stephen Rothwell
2008-07-16  5:35 ` Harvey Harrison
2008-07-09  3:13 Stephen Rothwell
2008-07-08  3:03 Stephen Rothwell
2008-07-08  8:18 ` Stephen Rothwell
2008-07-08  2:59 Stephen Rothwell
2008-07-08 14:33 ` Rafael J. Wysocki
2008-06-30  5:59 Stephen Rothwell
2008-06-30  6:09 ` Stephen Rothwell
2008-06-30  9:03   ` Ingo Molnar
2008-06-27  3:14 Stephen Rothwell
2008-06-26  4:21 Stephen Rothwell
2008-06-25  4:13 Stephen Rothwell
2008-06-23  4:19 Stephen Rothwell
2008-06-23 21:56 ` Ingo Molnar
2008-06-16  4:03 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=alpine.LFD.1.10.0806251516460.3014@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=robert.moore@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=yhlu.kernel@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).