netdev - Re: [PATCH 0/2] Remove T4 FCoE support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Jan 2015 15:25:04 +0100
From:	Hannes Reinecke <hare@...e.de>
To:	Praveen Madhavan <praveenm@...lsio.com>, netdev@...r.kernel.org,
	linux-scsi@...r.kernel.org
CC:	davem@...emloft.net, JBottomley@...allels.com, hch@...radead.org,
	hariprasad@...lsio.com, varun@...lsio.com
Subject: Re: [PATCH 0/2] Remove T4 FCoE support

On 01/15/2015 02:45 PM, Praveen Madhavan wrote:
> These patches removes FCoE support for chelsio T4 adapter.
> Please apply on net-next since depends on previous commits.
> 
> Praveen Madhavan (2):
>   csiostor:Remove T4 FCoE support.
>   csiostor:Removed file csio_hw_t4.c
> 
>  drivers/scsi/csiostor/Makefile       |   2 +-
>  drivers/scsi/csiostor/csio_hw.c      |  61 ++----
>  drivers/scsi/csiostor/csio_hw_chip.h |  43 ----
>  drivers/scsi/csiostor/csio_hw_t4.c   | 404 -----------------------------------
>  drivers/scsi/csiostor/csio_init.c    |   6 +-
>  drivers/scsi/csiostor/csio_wr.c      |  15 +-
>  6 files changed, 25 insertions(+), 506 deletions(-)
>  delete mode 100644 drivers/scsi/csiostor/csio_hw_t4.c
> 
Any particular reason for this?
It worked at one point, didn't it?

So why do you want to remove it?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare@...e.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html