On Fri, 27 Jan 2017 08:54:06 +0100
Greg KH wrote:
> On Thu, Jan 26, 2017 at 01:06:46PM -0500, David Miller wrote:
> > From: Stephen Hemminger
> > Date: Thu, 26 Jan 2017 10:04:05 -0800
> >
> > > I have a working set of patches to enable NAPI in the netvsc driver.
> > > The problem is that it r
On Fri, Jan 27, 2017 at 09:39:53AM -0800, Stephen Hemminger wrote:
> On Fri, 27 Jan 2017 08:54:06 +0100
> Greg KH wrote:
>
> > On Thu, Jan 26, 2017 at 01:06:46PM -0500, David Miller wrote:
> > > From: Stephen Hemminger
> > > Date: Thu, 26 Jan 2017 10:04:05 -0800
> > >
> > > > I have a working
On Thu, Jan 26, 2017 at 01:06:46PM -0500, David Miller wrote:
> From: Stephen Hemminger
> Date: Thu, 26 Jan 2017 10:04:05 -0800
>
> > 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 p
From: KY Srinivasan
Date: Thu, 26 Jan 2017 20:46:40 +
> 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-tre
> -Original Message-
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Thursday, January 26, 2017 10:04 AM
> To: da...@davemloft.net; KY Srinivasan ; Greg KH
>
> Cc: netdev@vger.kernel.org
> Subject: netvsc NAPI patch process
>
> I have a working set of patches to en
From: Stephen Hemminger
Date: Thu, 26 Jan 2017 10:04:05 -0800
> 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,
