From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753659AbdAZKJ6 (ORCPT <rfc822;w@1wt.eu>);
        Thu, 26 Jan 2017 05:09:58 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:46996 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752969AbdAZKJz (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 26 Jan 2017 05:09:55 -0500
Date: Thu, 26 Jan 2017 11:10:07 +0100
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
        "driverdev-devel@linuxdriverproject.org" 
        <driverdev-devel@linuxdriverproject.org>,
        KY Srinivasan <kys@microsoft.com>,
        Haiyang Zhang <haiyangz@microsoft.com>,
        Stephen Hemminger <sthemmin@microsoft.com>,
        "olaf@aepfle.de" <olaf@aepfle.de>,
        Rolf Neugebauer <rolf.neugebauer@docker.com>,
        "jasowang@redhat.com" <jasowang@redhat.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "apw@canonical.com" <apw@canonical.com>
Subject: Re: [PATCH] Drivers: hv: vmbus: finally fix
 hv_need_to_signal_on_read()
Message-ID: <20170126101007.GA4936@kroah.com>
References: <MWHPR03MB2669D6E05A877D07D09611EABF750@MWHPR03MB2669.namprd03.prod.outlook.com>
 <20170124080818.48c26a6c@xeon-e3>
 <MWHPR03MB266935324DC78F39EAA8B084BF770@MWHPR03MB2669.namprd03.prod.outlook.com>
 <20170126071653.GA26979@kroah.com>
 <MWHPR03MB2669FE7A96A50113199F0D60BF770@MWHPR03MB2669.namprd03.prod.outlook.com>
 <20170126074917.GA21753@kroah.com>
 <MWHPR03MB2669C095FE5FE637C6246040BF770@MWHPR03MB2669.namprd03.prod.outlook.com>
 <20170126091650.GA31667@kroah.com>
 <MWHPR03MB2669B010A23D49E816EB3625BF770@MWHPR03MB2669.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <MWHPR03MB2669B010A23D49E816EB3625BF770@MWHPR03MB2669.namprd03.prod.outlook.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Jan 26, 2017 at 09:31:32AM +0000, Dexuan Cui wrote:
> > From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> > > > From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> > > > > > > It's interesting v4.4.44 is not impacted, but actually it needs both the 2
> > > > patches:
> > > > > > > i.e. this patch, and the previous one:
> > > > > > > Commit a389fcfd2cb5 ("Drivers: hv: vmbus: Fix signaling logic in
> > > > > > hv_need_to_signal_on_read()")
> > > > > >
> > > > > > That patch does not apply to the 4.4-stable tree, which is why it was
> > > > > > not included there.  If you feel it should be included, please provide a
> > > > > > backport and send it to the stable@vger.kernel.org mailing list.
> > > > > >
> > > > > > greg k-h
> > > > >
> > > > > Thanks! I'll do the backport after this patch goes in the mainline.
> > > >
> > > > Why wait?
> > >
> > > I thought a patch must first appear in Linus's tree, before it can be
> > > back-ported to the stable tree?
> > 
> > Commit a389fcfd2cb5 _IS_ in Linus's tree, it was released in the 4.7-rc1
> > kernel, which happened in May of 2016.
> > 
> > greg k-h
> 
> Sorry, it looks I didn't make it clear. :-)
> 
> v4.4.44 needs 2 patches, i.e. a389fcfd2cb5, and this patch (which is not in
> Linus's tree yet).  Only backporting the first patch immediately is not enough
> and is also improper IMO, because the first patch introduces a new issue,
> which is being resolved by this patch. So my understanding is that I should
> backport the 2 patches together.

Ok, that makes a bit more sense, thanks.  I'll wait for your "real"
patch to hit Linus's tree then.

greg k-h