[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLUPR0301MB209880E89A61BA9E646DF4ECCC440@BLUPR0301MB2098.namprd03.prod.outlook.com>
Date: Fri, 10 Feb 2017 16:39:02 +0000
From: Stephen Hemminger <sthemmin@...rosoft.com>
To: Greg KH <gregkh@...uxfoundation.org>,
KY Srinivasan <kys@...rosoft.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"leann.ogasawara@...onical.com" <leann.ogasawara@...onical.com>,
Stephen Hemminger <stephen@...workplumber.org>
Subject: RE: [PATCH 05/13] vmbus: remove per channel state
-----Original Message-----
From: Greg KH [mailto:gregkh@...uxfoundation.org]
Sent: Friday, February 10, 2017 6:47 AM
To: KY Srinivasan <kys@...rosoft.com>
Cc: linux-kernel@...r.kernel.org; devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com; vkuznets@...hat.com; jasowang@...hat.com; leann.ogasawara@...onical.com; Stephen Hemminger <stephen@...workplumber.org>; Stephen Hemminger <sthemmin@...rosoft.com>
Subject: Re: [PATCH 05/13] vmbus: remove per channel state
On Sun, Feb 05, 2017 at 05:20:35PM -0700, kys@...hange.microsoft.com wrote:
> From: Stephen Hemminger <stephen@...workplumber.org>
>
> The netvsc no longer needs per channel state hook to track receive buffer.
>
> Signed-off-by: Stephen Hemminger <sthemmin@...rosoft.com>
> Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>
> ---
> include/linux/hyperv.h | 14 --------------
> 1 files changed, 0 insertions(+), 14 deletions(-)
This patch breaks the build badly, I don't know how it passed anyone's
build tests :(
The functions are still used in two different files.
I've applied the first 4 patches here, but really, I shouldn't have had
to bisect down to the offending patch.
ugh.
greg k-h
In the set I submitted was the patch to remove usage of per channel state in netvsc.
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
Powered by blists - more mailing lists