From: Michael Buesch <mb@bu3sch.de>
To: David Miller <davem@davemloft.net>
Cc: hch@infradead.org, jeff@garzik.org, mchan@broadcom.com,
netdev@vger.kernel.org, eliezert@broadcom.com,
lusinsky@broadcom.com, eilong@broadcom.com
Subject: Re: [RFC][BNX2X]: New driver for Broadcom 10Gb Ethernet.
Date: Wed, 8 Aug 2007 10:40:54 +0200 [thread overview]
Message-ID: <200708081040.55275.mb@bu3sch.de> (raw)
In-Reply-To: <20070807.160808.38709450.davem@davemloft.net>
On Wednesday 08 August 2007 01:08:08 David Miller wrote:
> From: Christoph Hellwig <hch@infradead.org>
> Date: Wed, 8 Aug 2007 00:04:59 +0100
>
> > Please take a look at kernel/irq/handle.c. The irq handler is
> > always called with the right dev_id argument. Everything would be a complete
> > nightmare to handle because you usually need to access the device private
> > data to check whether the shared irq is for this device.
>
> Absolutely.
>
> I can't believe we're even discussing something so obvious and
> wasting everyone's time.
>
>
Ok, then something "so obvious" is explained wrong in all off
the tutorials I read.
So it was _not_ that "obvious" to me. ok?
--
Greetings Michael.
next prev parent reply other threads:[~2007-08-08 8:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 8:31 [RFC][BNX2X]: New driver for Broadcom 10Gb Ethernet Michael Chan
2007-08-01 22:06 ` Michael Buesch
2007-08-01 22:28 ` Roland Dreier
2007-08-01 22:50 ` Jeff Garzik
2007-08-02 18:13 ` Eliezer Tamir
2007-08-02 18:09 ` Eliezer Tamir
2007-08-02 21:48 ` Michael Chan
2007-08-07 22:15 ` Jeff Garzik
2007-08-07 22:20 ` Michael Buesch
2007-08-07 23:04 ` Christoph Hellwig
2007-08-07 23:08 ` David Miller
2007-08-08 8:40 ` Michael Buesch [this message]
2007-08-07 23:04 ` 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=200708081040.55275.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=eliezert@broadcom.com \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=lusinsky@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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).