From: Grygorii Strashko <grygorii.strashko@ti.com>
To: David Miller <davem@davemloft.net>, <ivan.khoronzhuk@linaro.org>
Cc: <mugunthanvnm@ti.com>, <netdev@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<AStarikovskiy@topcon.com>
Subject: Re: [PATCH 0/2] net: ethernet: ti: cpsw: fix susp/resume
Date: Fri, 10 Feb 2017 12:05:07 -0600 [thread overview]
Message-ID: <ffaeb9fe-fd0a-3735-9f72-dded96de6e56@ti.com> (raw)
In-Reply-To: <20170209.204507.954952367013216032.davem@davemloft.net>
On 02/09/2017 07:45 PM, David Miller wrote:
> From: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.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@linaro.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.
>
Looks like the first fix is for net, but the second one is for net-next
I do not see
03fd01ad0eead23eb79294b6fb4d71dcac493855
"net: ethernet: ti: cpsw: don't duplicate ndev_running"
in net.
--
regards,
-grygorii
next prev parent reply other threads:[~2017-02-10 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 0:07 Ivan Khoronzhuk
2017-02-09 0:07 ` [PATCH 1/2] net: ethernet: ti: cpsw: fix cpsw assignment in resume Ivan Khoronzhuk
2017-02-09 0:07 ` [PATCH 2/2] net: ethernet: ti: cpsw: fix resume because of usage count Ivan Khoronzhuk
2017-02-09 22:21 ` [PATCH 0/2] net: ethernet: ti: cpsw: fix susp/resume David Miller
2017-02-09 22:54 ` Ivan Khoronzhuk
2017-02-10 1:45 ` David Miller
2017-02-10 18:05 ` Grygorii Strashko [this message]
2017-02-11 0:01 ` Ivan Khoronzhuk
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=ffaeb9fe-fd0a-3735-9f72-dded96de6e56@ti.com \
--to=grygorii.strashko@ti.com \
--cc=AStarikovskiy@topcon.com \
--cc=davem@davemloft.net \
--cc=ivan.khoronzhuk@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
/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
Powered by JetHome