All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: davem@davemloft.net, "K. Y. Srinivasan" <kys@microsoft.com>,
	Greg KH <greg@kroah.com>
Cc: netdev@vger.kernel.org
Subject: netvsc NAPI patch process
Date: Thu, 26 Jan 2017 10:04:05 -0800	[thread overview]
Message-ID: <20170126100405.0eac2dea@xeon-e3> (raw)

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?

             reply	other threads:[~2017-01-26 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 18:04 Stephen Hemminger [this message]
2017-01-26 18:06 ` netvsc NAPI patch process David Miller
2017-01-27  7:54   ` Greg KH
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=20170126100405.0eac2dea@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=kys@microsoft.com \
    --cc=netdev@vger.kernel.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.