All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Greg KH <greg@kroah.com>
Cc: Greg KH <gregkh@suse.de>,
	Brice Goglin <Brice.Goglin@ens-lyon.org>,
	torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
	Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@suse.de>
Subject: Re: State of the Linux PCI Subsystem for 2.6.23-rc8
Date: Thu, 27 Sep 2007 21:18:50 -0400	[thread overview]
Message-ID: <46FC567A.3030801@garzik.org> (raw)
In-Reply-To: <20070927153438.GC30419@kroah.com>

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 http://marc.info/?l=linux-pci&m=119072400008538&w=2 ?
>>> 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.

	Jeff




  reply	other threads:[~2007-09-28  1:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 21:00 State of the Linux PCI Subsystem for 2.6.23-rc8 Greg KH
2007-09-26 21:40 ` Brice Goglin
2007-09-26 21:39   ` Greg KH
2007-09-26 21:50     ` Brice Goglin
2007-09-27  7:22     ` Jeff Garzik
2007-09-27 15:34       ` Greg KH
2007-09-28  1:18         ` Jeff Garzik [this message]
2007-09-28  1:37           ` 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=46FC567A.3030801@garzik.org \
    --to=jeff@garzik.org \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.