From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>,
kristen.c.accardi@intel.com, Bernhard Kaindl <bk@suse.de>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [PATCH] PCI/Cardbus cards hidden, needs pci=assign-busses to fix
Date: Fri, 24 Feb 2006 14:16:41 +0100 [thread overview]
Message-ID: <20060224131641.GA11412@isilmar.linta.de> (raw)
In-Reply-To: <20060224014755.GD25787@kroah.com>
On Thu, Feb 23, 2006 at 05:47:55PM -0800, Greg KH wrote:
> > I guess if this is the only way in which we can do this, and nobody has any
> > better solutions then sure, it'll get people's machines going. We'll be
> > forever patching that table though.
> >
> > But _does_ anyone have any better solutions?
>
> This patch might not be needed at all, as per Kristen's recent comments
> on the linux-pci mailing list, and her small patch that is already in
> the -mm tree.
If you mean
Subject: [patch 3/4] pci: really fix parent's subordinate busnr
then no, that patch is not going to help: you can call
pci_fixup_parent_subordinate_busnr() as often as you want; it won't do
anything unless pcibios_assign_all_busses() is true.
Dominik
next prev parent reply other threads:[~2006-02-24 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 23:46 Problem with pci_fixups in drivers/pci/probe.c alan
2006-01-05 23:56 ` Dominik Brodowski
2006-01-06 13:48 ` Alan Cox
2006-02-16 22:06 ` [PATCH] PCI/Cardbus cards hidden, needs pci=assign-busses to fix Bernhard Kaindl
2006-02-18 9:41 ` Andrew Morton
2006-02-24 1:47 ` Greg KH
2006-02-24 13:16 ` Dominik Brodowski [this message]
2006-04-14 14:01 ` [PATCH] Cardbus cards hidden, fixup parent subordinate# carefully Bernhard Kaindl
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=20060224131641.GA11412@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bk@suse.de \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=kristen.c.accardi@intel.com \
--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
all inboxes | Powered by JetHome®