From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <willy@parisc-linux.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] [2/5] Improve 53c700 /proc/interrupt output
Date: Sat, 19 Mar 2005 09:53:07 -0600 [thread overview]
Message-ID: <1111247587.5525.7.camel@mulgrave> (raw)
In-Reply-To: <20050319035626.97A54496108@palinux.hppa>
On Fri, 2005-03-18 at 20:56 -0700, Matthew Wilcox wrote:
> Improve 53c700 /proc/interrupt output
>
> Request the IRQ in the name of the chip rather than the bus address.
This I don't really like for two reasons:
1) I don't know of any other driver that uses the actual chip name in
the interrupt (most use either the driver name or the module name)
2) As someone with a large number of these things in a single box,
knowing which actual device is going up in /proc/interrupts is valuable
to me
How about I look at abstracting the name so that the glue driver (in
your case lasi700) can set the name?
James
next prev parent reply other threads:[~2005-03-19 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 3:56 [PATCH] [2/5] Improve 53c700 /proc/interrupt output Matthew Wilcox
2005-03-19 15:53 ` James Bottomley [this message]
2005-03-19 16:23 ` Matthew Wilcox
2005-03-21 2:56 ` James Bottomley
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=1111247587.5525.7.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@parisc-linux.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