public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>, Jeff Garzik <jeff@garzik.org>
Cc: 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
Subject: Re: State of the Linux PCI Subsystem for 2.6.23-rc8
Date: Wed, 26 Sep 2007 14:39:31 -0700	[thread overview]
Message-ID: <20070926213931.GA24049@suse.de> (raw)
In-Reply-To: <46FAD1EA.6090504@ens-lyon.org>

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.

thanks,

greg k-h

  reply	other threads:[~2007-09-26 21:44 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 [this message]
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
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=20070926213931.GA24049@suse.de \
    --to=gregkh@suse.de \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox