Scott Wood wrote:
This driver can't handle an interrupt immediately after request_irq
You MUST assume that you will receive an interrupt immediately after
request_irq(). If fs_enet cannot handle that, then that is what wants
fixing.
Please send along a fix for this, rather than band-aiding
This driver can't handle an interrupt immediately after request_irq
(making it fail with CONFIG_DEBUG_SHIRQ), and has unshared interrupts
on all hardware I'm aware of.
Signed-off-by: Scott Wood <[EMAIL PROTECTED]>
---
drivers/net/fs_enet/fs_enet-main.c |2 +-
1 files changed, 1 insertions(+),
