Re: State of the Linux PCI Subsystem for 2.6.23-rc8

From: Greg KH
Date: Thu Sep 27 2007 - 21:39:23 EST

On Thu, Sep 27, 2007 at 09:18:50PM -0400, Jeff Garzik wrote:
> Greg KH wrote:
>> On Thu, Sep 27, 2007 at 03:22:35AM -0400, Jeff Garzik wrote:
>>> Greg KH wrote:
>>>> On Wed, Sep 26, 2007 at 11:40:58PM +0200, Brice Goglin wrote:
>>>>> Greg KH wrote:
>>>>>> Here's a summary of the current state of the Linux PCI subsystem, as
>>>>>> of
>>>>>> 2.6.23-rc8.
>>>>>> If the information in here is incorrect, or anyone knows of any
>>>>>> outstanding issues not listed here, please let me know.
>>>>>> List of outstanding regressions from 2.6.22:
>>>>>> - none known.
>>>>>> List of outstanding regressions from older kernel versions:
>>>>>> - none known.
>>>>> What about ?
>>>> That's not a regression, right? Tt's probably never worked for that
>>>> kind of box :)
>>>> I think the pci bus patches that are pending from Jeff Garzik should fix
>>>> up these issues. They are in one of his trees, and in the -mm release,
>>>> if you are able to test those.
>>> jgarzik/misc-2.6.git#pciseg has my only outstanding PCI stuff, which is a
>>> small x86[-64] PCI domain support patch. Mostly unrelated to the thread
>>> at hand, alas, even though it was touching that area.
>>> I need to a few changes required by Andi, who made several good points,
>>> then the PCI domains thing should be ready for upstream. I don't care
>>> much who merges it, you, Andi or me.
>> I'll take it, as I guess it should go through me, Andi is going to have
>> enough merge issues for 2.6.24 :)
>> I'll add them to my tree later today.
> Please don't pull 'pciseg' just yet... it needs the fixes Andi pointed
> out, namely, it should be turned on by default in x86 / x86-64 platform
> Kconfig, and have a boot-time method of disabling it.

Ok, let me know when you want me to pull it and I will. Or just send me
the patches by email, that's much easier for me :)


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at