From: Olaf Hering <olaf@aepfle.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"apw@canonical.com" <apw@canonical.com>,
"jasowang@redhat.com" <jasowang@redhat.com>
Subject: Re: [PATCH 2/2 net-next] hyperv: Support batched notification
Date: Thu, 12 Mar 2015 12:06:28 +0100 [thread overview]
Message-ID: <20150312110628.GC11353@aepfle.de> (raw)
In-Reply-To: <BY2PR0301MB07115FFD6E62E07CBAB0AED0A0190@BY2PR0301MB0711.namprd03.prod.outlook.com>
On Wed, Mar 11, KY Srinivasan wrote:
> This is the convention that we have used for patches submitted to
> David's tree.
I see, it refers to the directory name. In a bunch of backports it gives
the impression it affects the Hyper-V support as whole, while in fact a
given change is just for the network driver. Looks like I have to live
with that.
Olaf
prev parent reply other threads:[~2015-03-12 11:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 18:49 [PATCH 0/2 net-next] hyperv: Enable batched notification K. Y. Srinivasan
2015-03-10 18:49 ` K. Y. Srinivasan
2015-03-10 18:50 ` [PATCH 1/2 net-next] Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl() K. Y. Srinivasan
2015-03-10 18:50 ` K. Y. Srinivasan
2015-03-10 18:25 ` Greg KH
2015-03-10 18:50 ` [PATCH 2/2 net-next] hyperv: Support batched notification K. Y. Srinivasan
2015-03-11 3:34 ` Jason Wang
2015-03-11 16:41 ` KY Srinivasan
2015-03-11 16:41 ` KY Srinivasan
2015-03-11 9:23 ` Olaf Hering
2015-03-11 17:45 ` KY Srinivasan
2015-03-11 17:45 ` KY Srinivasan
2015-03-12 11:06 ` Olaf Hering [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=20150312110628.GC11353@aepfle.de \
--to=olaf@aepfle.de \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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.