public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Patrick Mansfield <patmans@us.ibm.com>
Subject: Re: PATCH [6/5]  qla2xxx: update version :)
Date: Wed, 13 Apr 2005 14:24:36 -0700	[thread overview]
Message-ID: <20050413212436.GC14857@plap.qlogic.org> (raw)
In-Reply-To: <1113425828.4933.39.camel@mulgrave>

On Wed, 13 Apr 2005, James Bottomley wrote:

> On Wed, 2005-04-13 at 13:50 -0700, Andrew Vasquez wrote:
> > -#define QLA2XXX_VERSION      "8.00.02b4-k"
> > +#define QLA2XXX_VERSION      "8.00.02b5-k"
> 
> so, erm, removing about 4,000 lines of code and embracing a new
> transport infrastructure doesn't even warrant a minor minor number
> change in the driver ... ?
> 

Ok, here's the deal -- QLogic's standard 8.01.00 driver contains the
following major additions:

* support for 4Gb ISPs
* FCIP support

I had considered going to 8.01.00-k or even 8.00.03-k for the upstream
kernel, but decided against it to minimize the potential for confusion
with users expecting comparable features and fixes with the two
drivers -- since there are QLogic standard 8.01.00 and 8.00.03
releases.

Yes, the upstream driver has just undergone some serious rework, and
in all honesty I'm rather ambivalent with respect to what the version
number is.  Nevertheless, this transition is going to be confusing and
had hoped that when the 4Gb support patch is added (after the dust
settled with the latest set of patches) the version number would then
pivot to 8.01.xx-k.

I'll feel fairly comfortable with the 4Gb upstream patches with about
another week of testing.

Anyway, given that, I'm open to suggestions...

--
av

  reply	other threads:[~2005-04-13 21:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 19:15 PATCH [0/5] qla2xxx: remote port rework Andrew Vasquez
2005-04-13 19:18 ` PATCH [1/5] qla2xxx: remove internal queuing Andrew Vasquez
2005-04-13 19:18 ` PATCH [2/5] qla2xxx: add remote port codes Andrew Vasquez
2005-04-13 21:40   ` Christoph Hellwig
2005-04-19  6:33     ` Andrew Vasquez
2005-04-19  7:27     ` Andrew Vasquez
2005-04-19 21:13       ` Christoph Hellwig
2005-05-20  6:17       ` Jeremy Higdon
2005-05-20 15:15         ` Andrew Vasquez
2005-05-27  7:51           ` Jeremy Higdon
2005-04-17 15:18   ` James Bottomley
2005-04-13 19:18 ` PATCH [3/5] qla2xxx: remove lun discovery codes Andrew Vasquez
2005-04-13 19:19 ` PATCH [4/5] qla2xxx: cleanup DMA mappings Andrew Vasquez
2005-04-13 21:34   ` Christoph Hellwig
2005-04-15 18:06     ` Andrew Vasquez
2005-04-13 19:19 ` PATCH [5/5] qla2xxx: remove /proc interface Andrew Vasquez
2005-04-13 19:42 ` PATCH [0/5] qla2xxx: remote port rework Matthew Wilcox
2005-04-13 20:50 ` PATCH [6/5] qla2xxx: update version :) Andrew Vasquez
2005-04-13 20:57   ` James Bottomley
2005-04-13 21:24     ` Andrew Vasquez [this message]
2005-04-19 21:15       ` Christoph Hellwig
2005-04-22  7:22         ` Andrew Vasquez
2005-04-24 10:53           ` Christoph Hellwig
2005-04-13 21:17   ` Christoph Hellwig
2005-04-15 17:38     ` Andrew Vasquez

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=20050413212436.GC14857@plap.qlogic.org \
    --to=andrew.vasquez@qlogic.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.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