From: keerthy <j-keerthy@ti.com>
To: David Miller <davem@davemloft.net>
Cc: <ivan.khoronzhuk@linaro.org>, <andrew@lunn.ch>,
<ilias.apalodimas@linaro.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<t-kristo@ti.com>, <grygorii.strashko@ti.com>, <nsekhar@ti.com>
Subject: Re: [PATCH V2] net: ethernet: ti: cpsw: Fix suspend/resume break
Date: Tue, 25 Jun 2019 15:34:41 +0530 [thread overview]
Message-ID: <e8e07695-d3dc-6a67-aede-a84d6cd3dbcc@ti.com> (raw)
In-Reply-To: <20190624.072333.2300932810459542260.davem@davemloft.net>
On 6/24/2019 7:53 PM, David Miller wrote:
> From: Keerthy <j-keerthy@ti.com>
> Date: Mon, 24 Jun 2019 10:46:19 +0530
>
>> Commit bfe59032bd6127ee190edb30be9381a01765b958 ("net: ethernet:
>> ti: cpsw: use cpsw as drv data")changes
>> the driver data to struct cpsw_common *cpsw. This is done
>> only in probe/remove but the suspend/resume functions are
>> still left with struct net_device *ndev. Hence fix both
>> suspend & resume also to fetch the updated driver data.
>>
>> Fixes: bfe59032bd6127ee1 ("net: ethernet: ti: cpsw: use cpsw as drv data")
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>
> Applied but please make it clear that changes are targetting net-next in the
> future by saying "[PATCH net-next v2] ...." in your Subject line.
Sure will do that. Thanks.
>
> Thank you.
>
prev parent reply other threads:[~2019-06-25 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 5:16 [PATCH V2] net: ethernet: ti: cpsw: Fix suspend/resume break Keerthy
2019-06-24 14:23 ` David Miller
2019-06-25 10:04 ` keerthy [this message]
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=e8e07695-d3dc-6a67-aede-a84d6cd3dbcc@ti.com \
--to=j-keerthy@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=ilias.apalodimas@linaro.org \
--cc=ivan.khoronzhuk@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=t-kristo@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).