From: Jeff Garzik <jgarzik@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 0/3] x86 PCI domain support
Date: Tue, 06 Dec 2005 23:12:07 -0500 [thread overview]
Message-ID: <43966117.9040700@pobox.com> (raw)
In-Reply-To: <20051207023305.GA19746@kroah.com>
Greg KH wrote:
> On Tue, Dec 06, 2005 at 09:14:30PM -0500, Jeff Garzik wrote:
>
>>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?
>>
>>You were supposed to read my mind :) "immediately" meant "ok for
>>upstream when -rc cycle closes" :) The third patch I don't consider
>>ready for upstream, -rc or no.
>
>
> Ok, thanks. But I did just include the third patch in my tree, so it
> will get tested in -mm. If you don't want this to happen, just let me
> know and I'll drop it.
There's no ultimate harm in it, because nothing turns on
CONFIG_PCI_DOMAINS in x86[-64] yet...
Jeff
next prev parent reply other threads:[~2005-12-07 4:12 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
2005-12-07 2:14 ` Jeff Garzik
2005-12-07 2:33 ` Greg KH
2005-12-07 4:12 ` Jeff Garzik [this message]
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=43966117.9040700@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@suse.de \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--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