linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org
Subject: [2.6 patch] schedule the SCSI qlogicfc driver for removal
Date: Tue, 14 Feb 2006 01:14:09 +0100	[thread overview]
Message-ID: <20060214001409.GA17604@stusta.de> (raw)
In-Reply-To: <20060204225801.GD4528@stusta.de>

As usual, there isn't much feedback regarding problems with one driver 
from people using an obsolete driver for the same hardware.

So schedule the SCSI qlogicfc driver for removal and let the 
flames^Wfeedback begin...


Signed-off-by: Adrian Bunk <bunk@stusta.de>

---

 Documentation/feature-removal-schedule.txt |    7 +++++++
 drivers/scsi/qlogicfc.c                    |    1 +
 2 files changed, 8 insertions(+)

--- linux-2.6.16-rc2-mm1-full/Documentation/feature-removal-schedule.txt.old	2006-02-14 00:26:21.000000000 +0100
+++ linux-2.6.16-rc2-mm1-full/Documentation/feature-removal-schedule.txt	2006-02-14 00:28:12.000000000 +0100
@@ -153,0 +154,7 @@
+What:   SCSI qlogicfc driver
+When:   August 2006
+Why:    replaced by the qla2xxx driver
+Who:    Adrian Bunk <bunk@stusta.de>
+
+---------------------------
+
--- linux-2.6.16-rc2-mm1-full/drivers/scsi/qlogicfc.c.old	2006-02-14 00:29:41.000000000 +0100
+++ linux-2.6.16-rc2-mm1-full/drivers/scsi/qlogicfc.c	2006-02-14 00:34:43.000000000 +0100
@@ -724,6 +724,7 @@
 	dma_addr_t busaddr;
 	int i;
 
+	printk(KERN_WARNING "qlogicfc will be removed soon, please use the qla2xxx driver\n");
 
 	ENTER("isp2x00_detect");
 


  reply	other threads:[~2006-02-14  0:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051024014838.0dd491bb.akpm@osdl.org>
     [not found] ` <1130186927.6831.23.camel@localhost.localdomain>
2005-10-24 21:16   ` 2.6.14-rc5-mm1 Andrew Morton
2005-10-25 15:12     ` 2.6.14-rc5-mm1 Badari Pulavarty
2005-10-25 17:57       ` 2.6.14-rc5-mm1 Andrew Morton
2005-10-25 16:13     ` 2.6.14-rc5-mm1 Christoph Hellwig
2005-10-27 15:26     ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-27 15:44       ` 2.6.14-rc5-mm1 Badari Pulavarty
2005-10-27 16:48         ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-27 19:02       ` 2.6.14-rc5-mm1 Christoph Hellwig
2005-10-27 21:53         ` 2.6.14-rc5-mm1 Andrew Vasquez
2005-10-28 22:51           ` HEADS UP for QLA2100 users Christoph Hellwig
2005-10-28 23:03             ` Andrew Vasquez
2005-10-28 23:35               ` Badari Pulavarty
2006-02-04 22:58                 ` Adrian Bunk
2006-02-14  0:14                   ` Adrian Bunk [this message]
2006-02-14 17:43                     ` [2.6 patch] schedule the SCSI qlogicfc driver for removal Christoph Hellwig
2006-03-25 18:04                       ` Adrian Bunk
2005-10-29 19:59 ` 2.6.14-rc5-mm1: SAS: compile error with gcc 2.95 Adrian Bunk
2005-10-29 20:15   ` Luben Tuikov

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=20060214001409.GA17604@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=andrew.vasquez@qlogic.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pbadari@gmail.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).