public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: Greg KH <greg@kroah.com>, Jeff Garzik <jgarzik@pobox.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86 PCI domain support
Date: Tue, 6 Dec 2005 17:41:02 -0800	[thread overview]
Message-ID: <20051207014102.GA19170@suse.de> (raw)
In-Reply-To: <20051207013201.GZ11190@wotan.suse.de>

On Wed, Dec 07, 2005 at 02:32:02AM +0100, Andi Kleen wrote:
> On Tue, Dec 06, 2005 at 04:39:22PM -0800, Greg KH wrote:
> > On Sat, Dec 03, 2005 at 03:11:54PM -0500, Jeff Garzik wrote:
> > > The first two patches could go in immediately, the last should probably 
> > > wait a bit...
> > 
> > What is the rush?  These seem pretty late for the -rc series :)
> > 
> > I'll send them in after 2.6.15 is out, is that ok?
> 
> It's ok, but the two related workaround patches I posted earlier should
> go into .15 (because they fix broken boot on some machines) 

Ok, that's fine.  Thanks for fixing those issues, I appreciate it.

greg k-h

  reply	other threads:[~2005-12-07  1:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03  1:39 [PATCH 0/3] x86 PCI domain support Jeff Garzik
2005-12-03  1:39 ` [PATCH 1/3] x86 PCI domain support: a humble fix Jeff Garzik
2005-12-03  1:40 ` [PATCH 2/3] x86 PCI domain support: struct pci_sysdata Jeff Garzik
2005-12-03  1:40 ` [PATCH 3/3] x86 PCI domain support: the meat Jeff Garzik
2005-12-03  1:42 ` [PATCH 0/3] x86 PCI domain support Jeff Garzik
2005-12-03  3:15 ` Andi Kleen
2005-12-03 20:11   ` Jeff Garzik
2005-12-03 21:03     ` Greg KH
2005-12-07  0:39     ` Greg KH
2005-12-07  1:32       ` Andi Kleen
2005-12-07  1:41         ` Greg KH [this message]
2005-12-07  2:14       ` Jeff Garzik
2005-12-07  2:33         ` Greg KH
2005-12-07  4:12           ` Jeff Garzik
2005-12-07  5:23             ` Greg KH

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=20051207014102.GA19170@suse.de \
    --to=gregkh@suse.de \
    --cc=ak@suse.de \
    --cc=greg@kroah.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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