From: Haiyang Zhang <haiyangz@linuxonhyperv.com>
To: sashal@kernel.org
Cc: haiyangz@microsoft.com, kys@microsoft.com,
sthemmin@microsoft.com, olaf@aepfle.de, vkuznets@redhat.com,
davem@davemloft.net, netdev@vger.kernel.org,
devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: [PATCH hyperv-fixes,0/3] fixes for hash key setting issues
Date: Tue, 15 Jan 2019 00:51:41 +0000 [thread overview]
Message-ID: <20190115005144.4494-1-haiyangz@linuxonhyperv.com> (raw)
From: Haiyang Zhang <haiyangz@microsoft.com>
Using ethtool to change Hash key failed on Linux VM runnig on
Hyper-V. This patch set fix them.
It targets Hyper-V tree, hyperv-fixes branch managed by
Sasha Levin <sashal@kernel.org>.
Haiyang Zhang (3):
Fix ethtool change hash key error
Refactor assignments of struct netvsc_device_info
Fix hash key value reset after other ops
drivers/net/hyperv/hyperv_net.h | 10 ++-
drivers/net/hyperv/netvsc.c | 2 +-
drivers/net/hyperv/netvsc_drv.c | 139 +++++++++++++++++++-----------
drivers/net/hyperv/rndis_filter.c | 34 ++++++--
4 files changed, 123 insertions(+), 62 deletions(-)
--
2.19.1
next reply other threads:[~2019-01-15 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 0:51 Haiyang Zhang [this message]
2019-01-15 0:51 ` [PATCH hyperv-fixes,0/3] fixes for hash key setting issues Haiyang Zhang
2019-01-15 0:51 ` [PATCH hyperv-fixes,1/3] Fix ethtool change hash key error Haiyang Zhang
2019-01-15 0:51 ` Haiyang Zhang
2019-01-19 1:11 ` Michael Kelley
2019-01-15 0:51 ` [PATCH hyperv-fixes,2/3] Refactor assignments of struct netvsc_device_info Haiyang Zhang
2019-01-19 1:13 ` Michael Kelley
2019-01-15 0:51 ` [PATCH hyperv-fixes,3/3] Fix hash key value reset after other ops Haiyang Zhang
2019-01-15 0:51 ` Haiyang Zhang
2019-01-19 1:14 ` Michael Kelley
2019-01-17 20:20 ` [PATCH hyperv-fixes,0/3] fixes for hash key setting issues Sasha Levin
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=20190115005144.4494-1-haiyangz@linuxonhyperv.com \
--to=haiyangz@linuxonhyperv.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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;
as well as URLs for NNTP newsgroup(s).