From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Morton <akpm@osdl.org>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-scsi@vger.kernel.org, promise_linux@promise.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.16-rc6] Promise SuperTrak driver
Date: Tue, 14 Mar 2006 13:04:30 -0700 [thread overview]
Message-ID: <20060314200430.GW1653@parisc-linux.org> (raw)
In-Reply-To: <20060313154236.32293cf9.akpm@osdl.org>
On Mon, Mar 13, 2006 at 03:42:36PM -0800, Andrew Morton wrote:
> > +#include <linux/irq.h>
>
> Can't include linux/irq.h from generic code (we really ought to fix that).
In a sense we have -- everybody should include <linux/interrupt.h> and
not <*/irq.h>. Perhaps we need to poison the includes.
> > +static inline u16 shasta_alloc_tag(u32 *bitmap)
> > +{
> > + u16 i;
> > + for (i = 0; i < TAG_BITMAP_LENGTH; i++)
> > + if (!((*bitmap) & (1 << i))) {
> > + *bitmap |= (1 << i);
> > + return i;
> > + }
> > +
> > + return TAG_BITMAP_LENGTH;
> > +}
>
> This is too large to be inlined.
And if I read the driver right, is unnecessary code. It could just use
the midlayer tag code (ok, not scsi_populate_tag_msg() which is
SPI-specific, but scsi_activate_tcq(), scsi_deactivate_tcq(),
scsi_find_tag(), scsi_set_tag_type(), and scsi_get_tag_type() should all
work, being thin wrappers around the block layer functionality.
next prev parent reply other threads:[~2006-03-14 20:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 22:41 [PATCH 2.6.16-rc6] Promise SuperTrak driver Jeff Garzik
2006-03-13 23:42 ` Andrew Morton
2006-03-14 10:50 ` Jan-Benedict Glaw
2006-03-14 20:04 ` Matthew Wilcox [this message]
2006-03-16 23:55 ` Adrian Bunk
[not found] <NONAMEBK04QBh0TzlYb000006b5@nonameb.ptu.promise.com>
2006-03-31 15:21 ` Jeff Garzik
[not found] <NONAMEBSkcJse1fTvOS000001bc@nonameb.ptu.promise.com>
2006-03-16 5:11 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 13:17 Ed Lin
2006-03-13 10:38 Ed Lin
2006-03-14 3:20 ` Andrew Morton
2006-03-14 7:13 ` Jeff Garzik
2006-03-14 9:18 ` Arjan van de Ven
2006-03-14 9:27 ` Jeff Garzik
2006-03-14 9:40 ` Arjan van de Ven
2006-03-14 15:12 ` Bob Copeland
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=20060314200430.GW1653@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=promise_linux@promise.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).