[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170209.204507.954952367013216032.davem@davemloft.net>
Date: Thu, 09 Feb 2017 20:45:07 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: ivan.khoronzhuk@...aro.org
Cc: mugunthanvnm@...com, grygorii.strashko@...com,
netdev@...r.kernel.org, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, AStarikovskiy@...con.com
Subject: Re: [PATCH 0/2] net: ethernet: ti: cpsw: fix susp/resume
From: Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>
Date: Fri, 10 Feb 2017 00:54:24 +0200
> On Thu, Feb 09, 2017 at 05:21:26PM -0500, David Miller wrote:
>> From: Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>
>> Date: Thu, 9 Feb 2017 02:07:34 +0200
>>
>> > These two patches fix suspend/resume chain.
>>
>> Patch 2 doesn't apply cleanly to the 'net' tree, please
>> respin this series.
>
> Strange, I've just checked it on net-next/master, it was applied w/o any
> warnings.
It makes no sense to test "net-next" when I am telling you that it is
the "net" tree it doesn't apply to.
This is a bug fix, so it should be targetting the "net" tree.
Powered by blists - more mailing lists