From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: Christoph Hellwig <hch@lst.de>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Giridhar Malavali <giridhar.malavali@qlogic.com>,
James Bottomley <JBottomley@Parallels.com>,
Roland Dreier <roland@purestorage.com>,
Joern Engel <joern@logfs.org>,
Madhuranath Iyengar <mni@risingtidesystems.com>
Subject: Re: [RFC-v4 0/3] qla2xxx: v3.4 target mode LLD changes + tcm_qla2xxx fabric module
Date: Fri, 23 Dec 2011 13:59:34 -0800 [thread overview]
Message-ID: <1324677574.16979.109.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20111222222520.GP22063@plapa.qlogic.org>
On Thu, 2011-12-22 at 14:25 -0800, Andrew Vasquez wrote:
> On Wed, 21 Dec 2011, Christoph Hellwig wrote:
>
> > I think the most important item is to sort out the mess around the old
> > generation qla23xx support. The way the code currently sprinkles ifs
> > around that is a complete mess. Given that the qla23xx support has as
> > far as I know zero test coverage, and has been EOLed by qlogic I see
> > no reason to keep it around.
> >
> > Anyone disagreeing with that?
> >
>
> Christoph,
>
> >From an engineering and support perspective it doesn't make sense to
> keep the (unsupported and untested) pre-ISP24xx codes around. Going
> forward, once internal resources can be allocated, QLogic would like
> to see support for all ISP24xx and above hardware.
>
> Regards,
> Andrew Vasquez
>
Hi Andrew,
Thanks for the official clarification here from Qlogic wrt to pre 24xx
hardware support in qla_target.c. We will go ahead and begin dropping
the legacy support and plan to have all the old code removed for an
RFC-v5 series to be posted after the holidays.
Thank you,
--nab
next prev parent reply other threads:[~2011-12-23 21:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 2:02 [RFC-v4 0/3] qla2xxx: v3.4 target mode LLD changes + tcm_qla2xxx fabric module Nicholas A. Bellinger
2011-12-18 2:02 ` [RFC-v4 1/3] qla2xxx: Add LLD internal target-mode support Nicholas A. Bellinger
2011-12-19 22:59 ` Roland Dreier
2011-12-21 21:48 ` Nicholas A. Bellinger
2011-12-21 22:46 ` Roland Dreier
2011-12-18 2:02 ` [RFC-v4 2/3] qla2xxx: Enable 2xxx series LLD target mode support Nicholas A. Bellinger
2011-12-18 2:02 ` [RFC-v4 3/3] qla2xxx: Add tcm_qla2xxx fabric module for mainline target Nicholas A. Bellinger
2011-12-22 8:10 ` Roland Dreier
2011-12-23 21:51 ` Nicholas A. Bellinger
2012-01-02 21:38 ` Roland Dreier
2012-01-10 0:24 ` Nicholas A. Bellinger
2011-12-21 17:11 ` [RFC-v4 0/3] qla2xxx: v3.4 target mode LLD changes + tcm_qla2xxx fabric module Christoph Hellwig
2011-12-22 22:25 ` Andrew Vasquez
2011-12-23 21:59 ` Nicholas A. Bellinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-13 15:55 Bart Van Assche
2012-05-14 3:29 ` Nicholas A. Bellinger
2012-05-14 12:50 ` Bart Van Assche
2012-05-14 23:12 ` Nicholas A. Bellinger
2012-05-15 14:21 ` Bart Van Assche
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=1324677574.16979.109.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=JBottomley@Parallels.com \
--cc=andrew.vasquez@qlogic.com \
--cc=giridhar.malavali@qlogic.com \
--cc=hch@lst.de \
--cc=joern@logfs.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mni@risingtidesystems.com \
--cc=roland@purestorage.com \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).