From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, devel@linuxdriverproject.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2 0/3] netvsc: bug fixes
Date: Thu, 08 Jun 2017 11:46:33 -0400 (EDT) [thread overview]
Message-ID: <20170608.114633.2109283089315273289.davem@davemloft.net> (raw)
In-Reply-To: <20170607225349.28359-1-sthemmin@microsoft.com>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 7 Jun 2017 15:53:46 -0700
> These are bugfixes for netvsc driver in 4.12.
Looks good, series applied, thanks.
prev parent reply other threads:[~2017-06-08 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 22:53 [PATCH net v2 0/3] netvsc: bug fixes Stephen Hemminger
2017-06-07 22:53 ` [PATCH net v2 1/3] netvsc: fix rcu dereference warning from ethtool Stephen Hemminger
2017-06-07 22:53 ` [PATCH net v2 2/3] netvsc: fix net poll mode Stephen Hemminger
2017-06-07 22:53 ` [PATCH net v2 3/3] netvsc: move filter setting to rndis_device Stephen Hemminger
2017-06-08 15:46 ` David Miller [this message]
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=20170608.114633.2109283089315273289.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).