From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: RE: [ANNOUNCE]: megaraid driver version 2.20.0.1
Date: 20 Jul 2004 16:56:05 -0500 [thread overview]
Message-ID: <1090360566.1861.33.camel@mulgrave> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC897@exa-atlanta>
On Tue, 2004-07-20 at 16:21, Mukker, Atul wrote:
> Is there a existing driver using this interface.
All the device drivers that use the transport class DV use it. At the
moment, that's 53c700 and sym_2.
The philosophy for scsi drivers for a while has been to remove internal
queueing, which is why yours attracted my attention, so the question I
was asking is can you use these APIs instead of having to maintain this
internal queue?
> Also, are these two changes gating factor for the driver to be included in
> the kernel. I do not want to make driver releases too often, unless
> of-course there is a critical fix, since it reset the driver validation in
> our testing labs. I have marked this and the yield() fix for the next drop
> of the driver
Either the changes or a good explanation why they shouldn't be done,
yes. External release cycles aren't a good reason to press for kernel
acceptance.
James
next prev parent reply other threads:[~2004-07-20 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 21:21 [ANNOUNCE]: megaraid driver version 2.20.0.1 Mukker, Atul
2004-07-20 21:56 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-21 13:48 Mukker, Atul
2004-07-21 17:06 ` James Bottomley
2004-07-06 18:32 Mukker, Atul
2004-07-06 20:56 ` James Bottomley
2004-06-26 0:55 Mukker, Atul
2004-07-06 14:46 ` James Bottomley
2004-06-25 9:07 Mukker, Atul
2004-06-25 1:07 Mukker, Atul
2004-06-25 8:13 ` 'Christoph Hellwig'
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=1090360566.1861.33.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Atulm@lsil.com \
--cc=hch@infradead.org \
--cc=linux-scsi@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