public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Greg KH <gregkh@suse.de>
Cc: torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz,
	pcihpd-discuss@lists.sourceforge.net
Subject: Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5
Date: Wed, 8 Mar 2006 23:26:52 +0100	[thread overview]
Message-ID: <20060308222652.GR4006@stusta.de> (raw)
In-Reply-To: <20060306223545.GA20885@kroah.com>

On Mon, Mar 06, 2006 at 02:35:45PM -0800, Greg KH wrote:

> Here's a summary of the current state of the Linux PCI and PCI Hotplug
> subsystems as of 2.6.16-rc5
> 
> If the information in here is incorrect, or anyone knows of any
> outstanding issues not listed here, please let me know.
>...
> Was this summary useful for people?  Anything that I should add to it?

It is useful, but one thing seems to be missing:
Which patches do you intend to forward for 2.6.16 (if any)?

(pci-pci-quirk-for-asus-a8v-and-a8v-deluxe-motherboards.patch seems to
 be a candidate.)

> thanks,
> 
> greg k-h

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2006-03-08 22:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 22:35 State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 Greg KH
2006-03-06 22:47 ` Sam Ravnborg
2006-03-06 23:00   ` Greg KH
2006-03-08 22:26 ` Adrian Bunk [this message]
2006-03-08 22:50   ` Greg KH
2006-03-08 23:03     ` Linus Torvalds
2006-03-08 23:18       ` Greg KH
2006-03-08 23:30         ` Linus Torvalds
2006-03-09 18:40           ` Tomasz Torcz
2006-03-09 19:49             ` Linus Torvalds
2006-03-09 20:10               ` Ben Collins
2006-03-09 20:24                 ` Linus Torvalds
2006-03-15 16:03                   ` Ben Collins
2006-03-09 20:52                 ` Lee Revell
2006-03-09 21:06                   ` SMP on UP (Was Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5) Ben Collins
2006-03-09 21:47                     ` Lee Revell
2006-03-09 21:07                   ` State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 David S. Miller
2006-03-09 20:37               ` Arjan van de Ven
2006-03-09 20:46                 ` Dave Jones
2006-03-09 21:15                   ` Arjan van de Ven
2006-03-08 23:29       ` Andrew Morton
2006-03-08 23:45         ` Dave Hansen
2006-03-08 23:52           ` Andrew Morton
2006-03-09 10:24         ` Martin MOKREJŠ
2006-03-08 23:05     ` Adrian Bunk
2006-03-08 23:18       ` Lee Revell
2006-03-08 23:23         ` Greg KH
2006-03-08 23:34           ` Lee Revell
2006-03-08 23:40             ` Greg KH
2006-03-09  0:03               ` Lee Revell
2006-03-08 23:21       ` Greg KH
2006-03-09  4:01 ` Kenji Kaneshige
2006-03-09  5:34   ` Greg KH
2006-03-09  5:11 ` Lee Revell

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=20060308222652.GR4006@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --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