From: Stephen Hemminger <stephen@networkplumber.org>
To: kys@microsoft.com, haiyangz@microsoft.com, sthemmin@microsoft.com
Cc: devel@linuxdriverproject.org, netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] netvsc: transparent VF related cleanups
Date: Thu, 31 Aug 2017 16:16:11 -0700 [thread overview]
Message-ID: <20170831231613.15805-1-sthemmin@microsoft.com> (raw)
The first gets rid of unnecessary ref counting, and second
allows removing hv_netvsc driver even if VF present.
Stephen Hemminger (2):
netvsc: cleanup datapath switch
netvsc: allow driver to be removed even if VF is present
drivers/net/hyperv/netvsc_drv.c | 55 ++++++++++++-----------------------------
1 file changed, 16 insertions(+), 39 deletions(-)
--
2.11.0
next reply other threads:[~2017-08-31 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 23:16 Stephen Hemminger [this message]
2017-08-31 23:16 ` [PATCH net-next 1/2] netvsc: cleanup datapath switch Stephen Hemminger
2017-08-31 23:16 ` [PATCH net-next 2/2] netvsc: allow driver to be removed even if VF is present Stephen Hemminger
2017-09-02 3:31 ` [PATCH net-next 0/2] netvsc: transparent VF related cleanups 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=20170831231613.15805-1-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox