From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFT PATCH] ARM: pci: kill pcibios_msi_controller
Date: Thu, 23 Jul 2015 18:15:25 +0100 [thread overview]
Message-ID: <20150723171514.GA23324@red-moon> (raw)
In-Reply-To: <20150723151018.GY21967@google.com>
On Thu, Jul 23, 2015 at 04:10:18PM +0100, Bjorn Helgaas wrote:
> On Wed, Jul 22, 2015 at 01:49:29PM +0100, Lorenzo Pieralisi wrote:
>
> > > >> @@ -483,14 +471,25 @@ static void pcibios_init_hw(struct device *parent, struct hw_pci *hw,
> > > >> break;
> > > >> }
> > > >>
> > > >> - if (hw->scan)
> > > >> + if (hw->scan) {
> > > >> sys->bus = hw->scan(nr, sys);
> > > >> - else
> > > >> - sys->bus = pci_scan_root_bus(parent, sys->busnr,
> > > >> - hw->ops, sys, &sys->resources);
> > > >> + if (!sys->bus)
> > > >> + panic("PCI: unable to scan bus!");
> > >
> > > This was in the original code, but I have to ask: Do we really want to
> > > panic the kernel if we couldn't scan the bus? Worse case, the system
> > > won't be able to boot at all and will panic somewhere else anyway, but
> > > we should give the user a chance to understand what's happening...
> >
> > No, it was in the original code but I was very tempted to remove it
> > or merge the error paths and make it a warning, and that's what I am
> > going to do, unless someone complains (that panic statement has been there
> > forever).
>
> I agree the panic should be removed. I would do it in a separate patch
> since it's not related to your main objective here.
Ok, I will post v2 shortly.
Thanks !
Lorenzo
next prev parent reply other threads:[~2015-07-23 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 10:43 [RFT PATCH] ARM: pci: kill pcibios_msi_controller Lorenzo Pieralisi
2015-07-22 9:02 ` Lorenzo Pieralisi
2015-07-22 9:24 ` Marc Zyngier
2015-07-22 12:49 ` Lorenzo Pieralisi
2015-07-23 15:10 ` Bjorn Helgaas
2015-07-23 17:15 ` Lorenzo Pieralisi [this message]
2015-07-22 9:30 ` Zhou Wang
2015-07-22 10:15 ` Marc Zyngier
2015-07-22 12:52 ` Lorenzo Pieralisi
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=20150723171514.GA23324@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).