Kok, Auke wrote:
Personally, I think this is really really needed. I'm surprised that you
already didn't push this considering Andrew pulled this into -mm
immediately.
Since it affects a fragile area of e1000 for all [e1000] users, I much
prefer to err on the side of caution. I have a histo
Jeff Garzik wrote:
Auke Kok wrote:
From: Auke Kok <[EMAIL PROTECTED]>
DEBUG_SHIRQ code exposed that e1000 was not ready for incoming interrupts
after having called pci_request_irq. This obviously requires us to finish
our software setup which assigns the irq handler before we request the
irq.
Auke Kok wrote:
From: Auke Kok <[EMAIL PROTECTED]>
DEBUG_SHIRQ code exposed that e1000 was not ready for incoming interrupts
after having called pci_request_irq. This obviously requires us to finish
our software setup which assigns the irq handler before we request the
irq.
Signed-off-by: Auke
From: Auke Kok <[EMAIL PROTECTED]>
DEBUG_SHIRQ code exposed that e1000 was not ready for incoming interrupts
after having called pci_request_irq. This obviously requires us to finish
our software setup which assigns the irq handler before we request the
irq.
Signed-off-by: Auke Kok <[EMAIL PROTEC
