From: Matthew Wilcox <matthew@wil.cx>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Kristen Accardi <kristen.c.accardi@intel.com>,
pcihpd-discuss@lists.sourceforge.net,
acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
rajesh.shah@intel.com, greg@kroah.com, len.brown@intel.com
Subject: Re: [Pcihpd-discuss] Re: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
Date: Thu, 27 Oct 2005 13:46:11 -0600 [thread overview]
Message-ID: <20051027194611.GC8201@parisc-linux.org> (raw)
In-Reply-To: <1130441897.3027.18.camel@laptopd505.fenrus.org>
On Thu, Oct 27, 2005 at 09:38:17PM +0200, Arjan van de Ven wrote:
> On Thu, 2005-10-27 at 12:30 -0700, Kristen Accardi wrote:
> > Store the value of PCI_INTERRUPT_PIN in the pci_dev structure for use
> > later. This is useful for pci hotplug. When a device is "surprise"
> > removed, the pci config space is no longer available. However,
> > the pin value is needed to correctly disable the irq for the device.
>
> Hmmm maybe it's just me..... but... isn't that both advisory and
> entirely unrelated to any kind of real interrupt thing? Eg dev->irq is
> there already and works even in the sight of IO-APICs etc etc...
With surprise hotplug, we can't read the pin from the card any more...
prev parent reply other threads:[~2005-10-27 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 19:30 [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev Kristen Accardi
2005-10-27 19:38 ` Arjan van de Ven
2005-10-27 19:46 ` Matthew Wilcox [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=20051027194611.GC8201@parisc-linux.org \
--to=matthew@wil.cx \
--cc=acpi-devel@lists.sourceforge.net \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=kristen.c.accardi@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rajesh.shah@intel.com \
/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