netdev - RE: netvsc NAPI patch process

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]

Message-ID: <DM5PR03MB249073BDE0362C6A7051AA8EA0770@DM5PR03MB2490.namprd03.prod.outlook.com>
Date:   Thu, 26 Jan 2017 20:46:40 +0000
From:   KY Srinivasan <kys@...rosoft.com>
To:     Stephen Hemminger <stephen@...workplumber.org>,
        "davem@...emloft.net" <davem@...emloft.net>,
        Greg KH <greg@...ah.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: netvsc NAPI patch process



> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@...workplumber.org]
> Sent: Thursday, January 26, 2017 10:04 AM
> To: davem@...emloft.net; KY Srinivasan <kys@...rosoft.com>; Greg KH
> <greg@...ah.com>
> Cc: netdev@...r.kernel.org
> Subject: netvsc NAPI patch process
> 
> I have a working set of patches to enable NAPI in the netvsc driver.
> The problem is that it requires a set of patches to vmbus layer as well.
> Since vmbus patches have been going through char-misc-next tree rather
> than net-next, it is difficult to stage these.

In the past, we have done this in two stages - get the supporting vmbus patches into
Greg's tree first and in the next merge cycle get the netvsc patches in. Why not continue to
do what we have done in the past to address cross-tree dependencies.

Regards,

K. Y 
> 
> How about if I send the vmbus patches through normal driver-devel
> upstream
> and during the 4.10 merge window send the last 3 patches for NAPI for linux-
> net
> tree to get into 4.10?