From: Dave Hansen <haveblue@us.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: christopher.leech@intel.com, scott.feldman@intel.com,
linux-kernel@vger.kernel.org
Subject: [PATCH] fix e1000 after irq craziness
Date: Mon, 29 Jul 2002 11:49:47 -0700 [thread overview]
Message-ID: <3D458E4B.4030702@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 120 bytes --]
I just duplicated the method used in:
drivers/net/tulip/de2104x.c
Compiles for me.
--
Dave Hansen
haveblue@us.ibm.com
[-- Attachment #2: e1000-irqfix-2.5.29-0.patch --]
[-- Type: text/plain, Size: 427 bytes --]
diff -ur linux-2.5.29-clean/drivers/net/e1000/e1000_main.c linux-2.5.29/drivers/net/e1000/e1000_main.c
--- linux-2.5.29-clean/drivers/net/e1000/e1000_main.c Fri Jul 26 19:58:36 2002
+++ linux-2.5.29/drivers/net/e1000/e1000_main.c Mon Jul 29 11:43:18 2002
@@ -1699,7 +1699,7 @@
{
atomic_inc(&adapter->irq_sem);
E1000_WRITE_REG(&adapter->hw, IMC, ~0);
- synchronize_irq();
+ synchronize_irq(adapter->netdev->irq);
}
/**
reply other threads:[~2002-07-29 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D458E4B.4030702@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=christopher.leech@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).