From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-sparc@vger.kernel.org,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: sym2 on sparc
Date: 02 Oct 2004 09:33:13 -0400 [thread overview]
Message-ID: <1096724000.2157.1.camel@mulgrave> (raw)
In-Reply-To: <20041001182056.GI16153@parcelfarce.linux.theplanet.co.uk>
On Fri, 2004-10-01 at 14:20, Matthew Wilcox wrote:
> Could someone with a symbios 53c8xx chip test this patch? It works
> on non-sparc. If I don't hear of any problems, it'll be in the next
> driver update.
Do we have to do this?
Putting architecture specific knowledge into a device driver is almost
never a good thing to do. If all you want to do is print out the IRQ
designation, I suspect this is a generic problem, not a sym2 specific
problem, so what we need is something like an irq_to_string()
abstraction.
James
next prev parent reply other threads:[~2004-10-02 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 18:20 sym2 on sparc Matthew Wilcox
2004-10-02 13:33 ` James Bottomley [this message]
2004-10-02 14:44 ` Matthew Wilcox
2004-10-02 23:41 ` David S. Miller
2004-10-08 11:25 ` William Lee Irwin III
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=1096724000.2157.1.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sparc@vger.kernel.org \
--cc=matthew@wil.cx \
/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).