netdev - [PATCH V2 0/20] qlcnic: patches for new adapter

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-next>] [day] [month] [year] [list]

Message-Id: <1350635858-27549-1-git-send-email-sony.chacko@qlogic.com>
Date:	Fri, 19 Oct 2012 04:37:18 -0400
From:	Sony Chacko <sony.chacko@...gic.com>
To:	davem@...emloft.net
Cc:	netdev@...r.kernel.org, Dept_NX_Linux_NIC_Driver@...gic.com,
	Sony Chacko <sony.chacko@...gic.com>
Subject: [PATCH V2 0/20] qlcnic: patches for new adapter - Qlogic 83XX CNA

From: Sony Chacko <sony.chacko@...gic.com>

> From: David Miller [mailto:davem@...emloft.net]
> Sent: Thursday, September 20, 2012 3:47 PM
> To: Sony Chacko
> Cc: netdev; Dept-NX Linux NIC Driver
> Subject: Re: [PATCH v1 0/19] qlcnic: patches for new adapter - Qlogic 
> 83XX CNA
> 
> I tired reviewing this driver just for coding style issues after just 
> looking at two or three of them.
> 
> I haven't even begun to think about the actual technical semantics and 
> correctness of these patches.  I doubt anyone else in the community 
> had either, and that won't even begin to happen until the coding style 
> issues are rectified.

Previous version of the patch set had lot style issues.
We have fixed the style issues without blindly relying on scripts. 

The following patch set will restructure existing Qlogic 82XX adapter driver
to create a common driver for 82XX and the new CNA - Qlogic 83XX.

Patches 1 to 13 - restructures existing 82XX adapter driver.
Patches 13 to 20 - 83XX adapter features.

Please apply the updated 20 patch series to net-next.

Thanks,
Sony
--
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