Re: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev

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...


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [Pcihpd-discuss] Re: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
    • From: Matthew Wilcox <[email protected]>

• References:
  • [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
    • From: Kristen Accardi <[email protected]>

• Prev by Date: [patch 2/3] apci: use stored value of pin from pci_dev
• Next by Date: Re: [Pcihpd-discuss] Re: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
• Previous by thread: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
• Next by thread: Re: [Pcihpd-discuss] Re: [patch 0/3] pci: store PCI_INTERRUPT_PIN in pci_dev
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]