From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Hemminger <sthemmin@microsoft.com>
Cc: KY Srinivasan <kys@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"leann.ogasawara@canonical.com" <leann.ogasawara@canonical.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH 05/13] vmbus: remove per channel state
Date: Fri, 10 Feb 2017 18:06:45 +0100 [thread overview]
Message-ID: <20170210170645.GC24378@kroah.com> (raw)
In-Reply-To: <BLUPR0301MB209880E89A61BA9E646DF4ECCC440@BLUPR0301MB2098.namprd03.prod.outlook.com>
On Fri, Feb 10, 2017 at 04:39:02PM +0000, Stephen Hemminger wrote:
> In the set I submitted was the patch to remove usage of per channel state in netvsc.
Ah.
> KY dropped it, because it already is in net-next. So this patch can wait until net-next is merged.
> The current split tree process is a pain and causes slow development cycles
Ick, I offered up a way to do this, but it doesn't look like KY or
anyone else took me up on it :(
sorry,
greg k-h
next prev parent reply other threads:[~2017-02-10 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1486340387-419-1-git-send-email-kys@exchange.microsoft.com>
[not found] ` <1486340443-515-5-git-send-email-kys@exchange.microsoft.com>
2017-02-10 14:46 ` [PATCH 05/13] vmbus: remove per channel state Greg KH
2017-02-10 16:39 ` Stephen Hemminger
2017-02-10 17:06 ` Greg KH [this message]
2017-02-12 5:55 ` KY Srinivasan
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=20170210170645.GC24378@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=stephen@networkplumber.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