netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: kys@microsoft.com
Cc: gregkh@linuxfoundation.org, olaf@aepfle.de,
	netdev@vger.kernel.org, jasowang@redhat.com,
	linux-kernel@vger.kernel.org, apw@canonical.com,
	devel@linuxdriverproject.org
Subject: Re: [PATCH V3 0/2 net-next] hyperv: Enable batched notification
Date: Tue, 17 Mar 2015 17:37:21 -0400 (EDT)	[thread overview]
Message-ID: <20150317.173721.927219759019408047.davem@davemloft.net> (raw)
In-Reply-To: <BY2PR0301MB07111A928395465732E9F4F0A0030@BY2PR0301MB0711.namprd03.prod.outlook.com>

From: KY Srinivasan <kys@microsoft.com>
Date: Tue, 17 Mar 2015 20:07:10 +0000

> I pulled down the net-next tree and the issue is with the first patch:
> 0001-Drivers-hv-vmbus-Export-the-vmbus_sendpacket_pagebuf.patch
> 
> The net-next tree is not current with Greg's tree and this patch is on code that
> is in Greg's tree. This patch merely exports an API that is already in Greg's tree.
> Greg wanted me to take this patch through your tree since the only user
> of this functionality is the network driver. Any suggestions on how I should 
> proceed here.
> 
> The second patch:
> 0002-hyperv-Support-batched-notification.patch
> 
> applies cleanly to your tree.

Don't create cross-tree dependencies like this.

I'm not pulling in Greg's tree to get a dependency like this.

And if I don't, I can't apply patch #2 because it will fail to
build.

  reply	other threads:[~2015-03-17 21:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 16:02 [PATCH V3 0/2 net-next] hyperv: Enable batched notification K. Y. Srinivasan
2015-03-17 16:02 ` [PATCH V3 1/2 net-next] Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl() K. Y. Srinivasan
2015-03-17 16:02   ` [PATCH V3 2/2 net-next] hyperv: Support batched notification K. Y. Srinivasan
2015-03-18  3:08     ` Jason Wang
2015-03-19 16:53       ` KY Srinivasan
     [not found]         ` <BY2PR0301MB07114336B35924D353108197A0010@BY2PR0301MB0711.namprd03.prod.out look.com>
2015-03-20  5:57           ` Jason Wang
2015-03-20 14:01             ` KY Srinivasan
2015-03-17 19:23 ` [PATCH V3 0/2 net-next] hyperv: Enable " David Miller
2015-03-17 19:26   ` KY Srinivasan
2015-03-17 20:07     ` KY Srinivasan
2015-03-17 21:37       ` David Miller [this message]
2015-03-17 21:39         ` 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=20150317.173721.927219759019408047.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=apw@canonical.com \
    --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 \
    --cc=olaf@aepfle.de \
    /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).