netdev - Re: [PATCH v2 net-next 0/5] SR-IOV and FW-dump enhancements

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

Message-Id: <20140509.131032.985580944351594696.davem@davemloft.net>
Date:	Fri, 09 May 2014 13:10:32 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	rajesh.borundia@...gic.com
Cc:	netdev@...r.kernel.org, Dept-HSGLinuxNICDev@...gic.com
Subject: Re: [PATCH v2 net-next 0/5] SR-IOV and FW-dump enhancements

From: Rajesh Borundia <rajesh.borundia@...gic.com>
Date: Fri, 9 May 2014 02:51:28 -0400

> This patch series contain following enhancements.
> 
> * SR-IOV enhancements:
>  - Allow SR-IOV VF's to probe in hypervisor. SR-IOV VF can be
>    uplinked to bridge/macvtap device with this change.
>  - Commands from VF are processed in process context
>    as it may sleep during PF-VF communication. Earlier
>    we use to process qlcnic_sriov_vf_set_multi function in 
>    process context but now we process individual commands.
>  - As SR-IOV VF's can be uplinked to bridge/macvtap device
>    support mac-learning to allow communication through 
>    embedded switch.
> 
> * FW-dump enhancement:
>  - Support to collect RDMEM section of firmware dump using 
>    PEX DMA method for 82xx series adapter. 
> 
> * Changes in v2:
>  - Removed unnecessary cast from void pointer to something
>    else and verified this issue in entire patch series as
>    per David Miller's suggestion.
> 
> Please apply this series to net-next.

Series applied, thanks.
--
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