From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org,
Alessio Igor Bogani <abogani@kernel.org>,
Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] scripts/modpost: check for bad refernces in .pci.fixups area
Date: Thu, 03 May 2012 20:29:25 +0200 [thread overview]
Message-ID: <4FA2CE85.8080006@linutronix.de> (raw)
In-Reply-To: <CAErSpo6kqfxvVU5JvS99-GCdeHHKceWcwnAjpd_gi=O34GCsfQ@mail.gmail.com>
On 05/03/2012 08:12 PM, Bjorn Helgaas wrote:
> Most of the things this finds are quirks for devices one could argue
> are not hot-pluggable, like northbridges, I/O APICs, etc. But some of
> those are becoming hot-pluggable, and I think it's too easy to make
> the wrong __init/__devinit decision, so I think the safest thing is to
> make them all __devinit.
I got here via a PCIe-bridge quirk. The bridge itself is not removed
but the quirk is executed after "echo 1 > remove" followed by rescan.
> Acked-by: Bjorn Helgaas<bhelgaas@google.com>
>
> I assume this will be merged via a kbuild tree; let me know if otherwise.
I tried to figured who is in charge here. I guess either Marek or
Alessio Bogani will take it. Atleast I have the PCI-ack here :)
> Will you post a follow-up patch to fix the PCI quirk annotations?
Since you are fine with it, let me try to prepare some.
Sebastian
prev parent reply other threads:[~2012-05-03 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 15:23 [PATCH] scripts/modpost: check for bad refernces in .pci.fixups area Sebastian Andrzej Siewior
2012-05-03 18:12 ` Bjorn Helgaas
2012-05-03 18:29 ` Sebastian Andrzej Siewior [this message]
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=4FA2CE85.8080006@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=abogani@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mmarek@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.