[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DM5PR2101MB10325F63F4BC3514D65B83C8FBBE0@DM5PR2101MB1032.namprd21.prod.outlook.com>
Date: Tue, 10 Apr 2018 13:49:36 +0000
From: Sasha Levin <Alexander.Levin@...rosoft.com>
To: Sasha Levin <Alexander.Levin@...rosoft.com>,
Mohammed Gamal <mgamal@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Stephen Hemminger <sthemmin@...rosoft.com>
CC: "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH 3/4] hv_netvsc: Ensure correct teardown message sequence
order
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 0ef58b0a05c1 hv_netvsc: change GPAD teardown order on older versions.
The bot has also determined it's probably a bug fixing patch. (score: 60.7987)
The bot has tested the following trees: v4.16.1.
v4.16.1: Failed to apply! Possible dependencies:
7992894c305e ("hv_netvsc: Split netvsc_revoke_buf() and netvsc_teardown_gpadl()")
--
Thanks,
Sasha
Powered by blists - more mailing lists