netdev - [PATCH v4 0/21] 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 for Android: free password hash cracker in your pocket

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

Message-Id: <1351556092-16417-1-git-send-email-sony.chacko@qlogic.com>
Date:	Mon, 29 Oct 2012 20:14:31 -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 v4 0/21] qlcnic: patches for new adapter - Qlogic 83XX CNA

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

> From: David Miller [mailto:davem@...emloft.net]
> Sent: Wednesday, October 24, 2012 8:11 PM
> To: Sony Chacko
> Cc: netdev; Dept-NX Linux NIC Driver
> Subject: Re: [PATCH V3 02/21] qlcnic: create seperate file for data path
> routines
> 
> From: Sony Chacko <sony.chacko@...gic.com>
> Date: Tue, 23 Oct 2012 18:30:53 -0400
> 
> > +static inline bool qlcnic_82xx_check(struct qlcnic_adapter *adapter)
> > +{
> > +	return (adapter->pdev->device ==
> PCI_DEVICE_ID_QLOGIC_QLE824X) ? 1 :
> > +0; }
> 
> "bool" is either "true" or "false", so return "true" or "false" rather than "1" or
> "0"

Re-submitting the patch set after making the changes as suggested above.

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 11 - restructures existing 82XX adapter driver.
Patches 12 to 21 - 83XX adapter features.

Please apply the updated 21 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