From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Stephen Hemminger <sthemmin@microsoft.com>
Cc: "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 05/14] netvsc: remove no longer needed receive staging buffers
Date: Fri, 10 Feb 2017 15:55:33 +0100 [thread overview]
Message-ID: <20170210145533.GE24594@kroah.com> (raw)
In-Reply-To: <BLUPR0301MB209810C0172361C40F9ABDCBCC430@BLUPR0301MB2098.namprd03.prod.outlook.com>
On Tue, Feb 07, 2017 at 12:32:12AM +0000, Stephen Hemminger wrote:
> The netvsc part is already in net-next. This patch is not needed.
> The part that removes the per-channel state can be in another patch.
I have no idea what that means to me here, nor what I need to do, so I'm
just deleting this email :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-10 14:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 16:28 [PATCH 00/14] hyperv: vmbus related patches Stephen Hemminger
2017-02-01 16:28 ` [PATCH 01/14] vmbus: use kernel bitops for traversing interrupt mask Stephen Hemminger
2017-02-01 16:28 ` [PATCH 02/14] vmbus: drop no longer used kick_q argument Stephen Hemminger
2017-02-01 16:28 ` [PATCH 03/14] vmbus: remove no longer used signal_policy Stephen Hemminger
2017-02-01 16:28 ` [PATCH 04/14] vmbus: remove unused kickq argument to sendpacket Stephen Hemminger
2017-02-01 16:28 ` [PATCH 05/14] netvsc: remove no longer needed receive staging buffers Stephen Hemminger
2017-02-05 23:40 ` KY Srinivasan via Virtualization
2017-02-07 0:32 ` Stephen Hemminger via Virtualization
[not found] ` <BLUPR0301MB209810C0172361C40F9ABDCBCC430@BLUPR0301MB2098.namprd03.prod.outlook.com>
2017-02-10 14:55 ` gregkh [this message]
2017-02-01 16:28 ` [PATCH 06/14] vmbus: remove per channel state Stephen Hemminger
2017-02-01 16:28 ` [PATCH 07/14] vmbus: callback is in softirq not workqueue Stephen Hemminger
2017-02-01 16:28 ` [PATCH 08/14] vmbus: put related per-cpu variable together Stephen Hemminger
2017-02-01 16:28 ` [PATCH 09/14] vmbus: change to per channel tasklet Stephen Hemminger
2017-02-01 16:28 ` [PATCH 10/14] vmbus: add direct isr callback mode Stephen Hemminger
2017-02-01 16:28 ` [PATCH 11/14] vmbus: remove conditional locking of vmbus_write Stephen Hemminger
2017-02-01 16:28 ` [PATCH 12/14] vmbus: expose hv_begin/end_read Stephen Hemminger
2017-02-01 16:29 ` [PATCH 13/14] vmbus: constify parameters where possible Stephen Hemminger
2017-02-01 16:29 ` [PATCH 14/14] vmbus: replace modulus operation with subtraction Stephen Hemminger
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=20170210145533.GE24594@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@linuxdriverproject.org \
--cc=sthemmin@microsoft.com \
--cc=virtualization@lists.linux-foundation.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 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).