From: Greg KH <greg@kroah.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: gregkh@suse.de, Adrian Bunk <bunk@stusta.de>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove the broken PCI_MULTITHREAD_PROBE option
Date: Tue, 27 Mar 2007 15:50:06 -0700 [thread overview]
Message-ID: <20070327225006.GC4478@kroah.com> (raw)
In-Reply-To: <20070327130351.51aff00e@gondolin.boeblingen.de.ibm.com>
On Tue, Mar 27, 2007 at 01:03:51PM +0200, Cornelia Huck wrote:
> On Tue, 27 Mar 2007 03:02:51 +0200,
> Adrian Bunk <bunk@stusta.de> wrote:
>
> > This patch removes the PCI_MULTITHREAD_PROBE option that had already
> > been marked as broken.
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > ---
> >
> > Documentation/pci.txt | 4 ---
> > drivers/base/dd.c | 41 ++-------------------------------------
> > drivers/pci/Kconfig | 25 -----------------------
> > drivers/pci/pci-driver.c | 15 --------------
> > include/linux/device.h | 1
> > 5 files changed, 3 insertions(+), 83 deletions(-)
>
> Greg, what about driver-core-per-subsystem-multithreaded-probing.patch?
> PCI_MULTITHREAD_PROBE shoudn't be broken with that, only in mainline?
Do you want to enable PCI multithreaded probing using your patch? I
don't think the world is ready for pci multithreaded probing as was
determined by the zillion of bug reports from people who like to enable
config options that state in big letters, "THIS WILL BREAK YOUR BOX"...
And I'm still questioning if we should add your patch at all, as I don't
think any other subsystems need it. Do you?
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-27 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 1:02 [2.6 patch] remove the broken PCI_MULTITHREAD_PROBE option Adrian Bunk
2007-03-27 11:03 ` Cornelia Huck
2007-03-27 22:50 ` Greg KH [this message]
2007-03-28 8:36 ` Cornelia Huck
2007-04-07 0:43 ` 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=20070327225006.GC4478@kroah.com \
--to=greg@kroah.com \
--cc=bunk@stusta.de \
--cc=cornelia.huck@de.ibm.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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