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 0/3] hv_netvsc: notification and namespace fixes
Date: Mon, 11 Jun 2018 12:44:53 -0700 [thread overview]
Message-ID: <20180611194456.8268-1-sthemmin@microsoft.com> (raw)
This set of patches addresses two set of fixes. First it backs out
the common callback model which was merged in net-next without
completing all the review feedback or getting maintainer approval.
Then it fixes the transparent VF management code to handle network
namespaces.
Stephen Hemminger (3):
hv_netvsc: drop common code until callback model fixed
hv_netvsc: fix network namespace issues with VF support
hv_netvsc: move VF to same namespace as netvsc device
drivers/net/hyperv/Kconfig | 1 -
drivers/net/hyperv/hyperv_net.h | 4 +-
drivers/net/hyperv/netvsc_drv.c | 242 ++++++++++++++++++++++++--------
3 files changed, 184 insertions(+), 63 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-11 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 19:44 Stephen Hemminger [this message]
2018-06-11 19:44 ` [PATCH net 1/3] hv_netvsc: drop common code until callback model fixed Stephen Hemminger
2018-06-11 19:44 ` [PATCH net 2/3] hv_netvsc: fix network namespace issues with VF support Stephen Hemminger
2018-06-12 9:51 ` Dan Carpenter
2018-06-12 15:10 ` Stephen Hemminger
2018-06-11 19:44 ` [PATCH net 3/3] hv_netvsc: move VF to same namespace as netvsc device Stephen Hemminger
2018-06-12 22:22 ` [PATCH net 0/3] hv_netvsc: notification and namespace fixes 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=20180611194456.8268-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 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.