From: "Andrew Vasquez" <andrew.vasquez@qlogic.com>
To: "Jeff Garzik" <jgarzik@pobox.com>, "Andrew Vasquez" <praka@san.rr.com>
Cc: "Mike Anderson" <andmike@us.ibm.com>,
"Michael Clark" <michael@metaparadigm.com>,
"David S. Miller" <davem@redhat.com>, <wli@holomorphy.com>,
<axboe@suse.de>, <akpm@digeo.com>, <linux-kernel@vger.kernel.org>,
<patmans@us.ibm.com>
Subject: RE: [PATCH] deadline io scheduler
Date: Fri, 27 Sep 2002 09:01:20 -0700 [thread overview]
Message-ID: <B179AE41C1147041AA1121F44614F0B004F771@AVEXCH02.qlogic.org> (raw)
> Andrew Vasquez wrote:
> > I hope this helps to clearup some of the haze and ambiguity
> > surrounding QLogic's work with the 6.x series driver, and perhaps
> > at the same time, prepares a medium for discussion regarding the 6.x
> > series driver.
>
> Wow, thanks for all that information, and it's great that you've
> integrated Arjan's work and feedback.
>
> There is one big question left unanswered... Where can the
> source for
> the latest version with all this wonderful stuff be found?
> :) I don't
> see a URL even for 6.01b5.
>
Sure, the 6.01b5 tarball can be found at:
http://download.qlogic.com/drivers/5642/qla2x00-v6.1b5-dist.tgz
In general all QLogic drivers are available from the following URL:
http://www.qlogic.com/support/drivers_software.asp
In my mind, a larger question is determining a balance between the
'Release Early, release often' mantra of Linux development and the
'kinder, more conservative pace' of business. For example, If we
cannot setup a 'patch/pre-beta' web-site locally at QLogic, I've
considered starting a SourceForge project or hosting it locally
through my ISP.
Regards,
Andrew Vasquez
next reply other threads:[~2002-09-27 15:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 16:01 Andrew Vasquez [this message]
2002-09-27 17:07 ` [PATCH] deadline io scheduler Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2002-09-25 17:20 Jens Axboe
2002-09-26 6:15 ` Andrew Morton
2002-09-26 6:27 ` David S. Miller
2002-09-26 6:44 ` Jens Axboe
2002-09-26 6:59 ` Jens Axboe
2002-09-26 7:06 ` William Lee Irwin III
2002-09-26 7:06 ` David S. Miller
2002-09-26 7:16 ` Jeff Garzik
2002-09-26 7:13 ` David S. Miller
2002-09-26 7:33 ` Jeff Garzik
2002-09-26 7:35 ` David S. Miller
2002-09-26 8:15 ` Michael Clark
2002-09-26 8:18 ` William Lee Irwin III
2002-09-26 17:41 ` Mike Anderson
2002-09-26 18:03 ` Jeff Garzik
2002-09-26 19:21 ` Mike Anderson
2002-09-27 5:41 ` Andrew Vasquez
2002-09-27 5:57 ` Jeff Garzik
2002-09-27 16:58 ` Mike Anderson
2002-09-26 22:41 ` Matt Porter
2002-09-26 22:35 ` Mark Bellon
2002-09-26 20:21 ` Thomas Tonino
2002-09-26 7:41 ` Jeff Garzik
2002-09-26 7:23 ` William Lee Irwin III
2002-09-26 7:11 ` Jeff Garzik
2002-09-26 7:14 ` William Lee Irwin III
2002-09-26 15:54 ` Patrick Mansfield
2002-09-30 8:15 ` Jens Axboe
2002-09-30 15:39 ` Patrick Mansfield
2002-09-30 16:08 ` Jens Axboe
2002-09-26 8:28 ` Daniel Pittman
2002-09-26 8:29 ` Jens Axboe
2002-09-26 23:23 ` Daniel Pittman
2002-09-30 8:10 ` Jens Axboe
2002-09-26 15:09 ` Rik van Riel
2002-09-26 7:12 ` Andrew Morton
2002-09-26 7:17 ` Jens Axboe
2002-09-26 7:34 ` Jens Axboe
2002-09-30 7:45 ` Pavel Machek
2002-10-02 5:35 ` Jens Axboe
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=B179AE41C1147041AA1121F44614F0B004F771@AVEXCH02.qlogic.org \
--to=andrew.vasquez@qlogic.com \
--cc=akpm@digeo.com \
--cc=andmike@us.ibm.com \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.com \
--cc=patmans@us.ibm.com \
--cc=praka@san.rr.com \
--cc=wli@holomorphy.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).