From: Roland Dreier <roland@topspin.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: long <tlnguyen@snoqualmie.dp.intel.com>,
linux-kernel@vger.kernel.org, ak@muc.de, akpm@osdl.org,
greg@kroah.com, jgarzik@pobox.com, tom.l.nguyen@intel.com,
zwane@linuxpower.ca
Subject: Re: [PATCH]2.6.7 MSI-X Update
Date: Sat, 26 Jun 2004 10:30:20 -0700 [thread overview]
Message-ID: <523c4i1b2r.fsf@topspin.com> (raw)
In-Reply-To: <20040626082713.GA11693@infradead.org> (Christoph Hellwig's message of "Sat, 26 Jun 2004 09:27:14 +0100")
Roland> As a concrete example, the e1000 net driver does
Roland> request_irq() in its e1000_up() function and free_irq() in
Roland> its e1000_down() function. Basically, the driver will do
Roland> request_irq() when the user does "ifconfig up" and
Roland> free_irq() when the user does "ifconfig down".
Christoph> Lots of networking drivers do that..
Yup, I just wanted to pick one definite example so I could point to
real function names, etc. (And also I wanted to pick a piece of
hardware that I happen to know is MSI-capable).
Thanks,
Roland
next prev parent reply other threads:[~2004-06-26 17:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 1:21 RE:[PATCH]2.6.7 MSI-X Update long
2004-06-26 0:30 ` [PATCH]2.6.7 " Roland Dreier
2004-06-26 1:38 ` Roland Dreier
2004-06-26 8:27 ` Christoph Hellwig
2004-06-26 17:30 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-19 15:36 Nguyen, Tom L
2004-07-15 15:46 Nguyen, Tom L
2004-07-13 22:02 long
2004-07-15 2:14 ` [PATCH]2.6.7 " Roland Dreier
2004-07-18 1:25 ` Roland Dreier
2004-06-24 16:29 Nguyen, Tom L
2004-06-23 22:03 Nguyen, Tom L
2004-06-24 1:42 ` Roland Dreier
2004-06-24 6:37 ` Zwane Mwaikambo
2004-06-24 7:27 ` Roland Dreier
2004-06-23 16:58 Nguyen, Tom L
2004-06-23 16:49 Nguyen, Tom L
2004-06-22 23:06 Nguyen, Tom L
2004-06-22 21:48 long
2004-06-22 23:57 ` Roland Dreier
2004-06-23 0:26 ` Jeff Garzik
2004-06-23 1:18 ` Roland Dreier
2004-06-23 3:45 ` Roland Dreier
2004-06-23 16:50 ` Roland Dreier
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=523c4i1b2r.fsf@topspin.com \
--to=roland@topspin.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tlnguyen@snoqualmie.dp.intel.com \
--cc=tom.l.nguyen@intel.com \
--cc=zwane@linuxpower.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.