From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: stephen@networkplumber.org, kys@microsoft.com, netdev@vger.kernel.org
Subject: Re: netvsc NAPI patch process
Date: Fri, 27 Jan 2017 08:54:06 +0100 [thread overview]
Message-ID: <20170127075406.GC31443@kroah.com> (raw)
In-Reply-To: <20170126.130646.2180422281199593870.davem@davemloft.net>
On Thu, Jan 26, 2017 at 01:06:46PM -0500, David Miller wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
> 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, it is difficult to stage these.
> >
> > 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?
>
> Another option is that the char-misc-next folks create a branch with just
> the commits you need for NAPI, I pull that into net-next, and then you
> can submit the NAPI changes to me.
I can easily do that, or I have no problem with the vmbus changes going
through the net-next tree, if they are sane (i.e. let me review them
please...) Which ever is easier for the networking developers, their
tree is much crazier than the tiny char-misc tree is :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-27 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 18:04 netvsc NAPI patch process Stephen Hemminger
2017-01-26 18:06 ` David Miller
2017-01-27 7:54 ` Greg KH [this message]
2017-01-27 17:39 ` Stephen Hemminger
2017-01-27 18:04 ` Greg KH
2017-01-26 20:46 ` KY Srinivasan
2017-01-26 20:48 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170127075406.GC31443@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=kys@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.