From: Joakim Zhang <qiangqing.zhang@nxp.com>
To: Jon Hunter <jonathanh@nvidia.com>, Jakub Kicinski <kuba@kernel.org>
Cc: "peppe.cavallaro@st.com" <peppe.cavallaro@st.com>,
"alexandre.torgue@foss.st.com" <alexandre.torgue@foss.st.com>,
"joabreu@synopsys.com" <joabreu@synopsys.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
"treding@nvidia.com" <treding@nvidia.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [RFC net-next] net: stmmac: should not modify RX descriptor when STMMAC resume
Date: Thu, 6 May 2021 06:33:39 +0000 [thread overview]
Message-ID: <DB8PR04MB67952FC590FEE5A327DA4C95E6589@DB8PR04MB6795.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1732e825-dd8b-6f24-6ead-104467e70a6c@nvidia.com>
> -----Original Message-----
> From: Jon Hunter <jonathanh@nvidia.com>
> Sent: 2021年4月23日 21:48
> To: Jakub Kicinski <kuba@kernel.org>; Joakim Zhang
> <qiangqing.zhang@nxp.com>
> Cc: peppe.cavallaro@st.com; alexandre.torgue@foss.st.com;
> joabreu@synopsys.com; davem@davemloft.net;
> mcoquelin.stm32@gmail.com; andrew@lunn.ch; f.fainelli@gmail.com;
> dl-linux-imx <linux-imx@nxp.com>; treding@nvidia.com;
> netdev@vger.kernel.org
> Subject: Re: [RFC net-next] net: stmmac: should not modify RX descriptor when
> STMMAC resume
>
>
> On 22/04/2021 16:56, Jakub Kicinski wrote:
> > On Thu, 22 Apr 2021 04:53:08 +0000 Joakim Zhang wrote:
> >> Could you please help review this patch? It's really beyond my
> >> comprehension, why this patch would affect Tegra186 Jetson TX2 board?
> >
> > Looks okay, please repost as non-RFC.
>
>
> I still have an issue with a board not being able to resume from suspend with
> this patch. Shouldn't we try to resolve that first?
Hi Jon,
Any updates about this? Could I repost as non-RFC?
Best Regards,
Joakim Zhang
> Jon
next prev parent reply other threads:[~2021-05-06 6:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 11:59 [RFC net-next] net: stmmac: should not modify RX descriptor when STMMAC resume Joakim Zhang
2021-04-19 15:12 ` Jon Hunter
2021-04-20 1:49 ` Joakim Zhang
2021-04-20 13:33 ` Jon Hunter
2021-04-22 4:53 ` Joakim Zhang
2021-04-22 15:56 ` Jakub Kicinski
2021-04-23 13:48 ` Jon Hunter
2021-05-06 6:33 ` Joakim Zhang [this message]
2021-05-07 14:22 ` Jon Hunter
2021-05-08 11:20 ` Joakim Zhang
2021-05-08 15:42 ` Florian Fainelli
2021-05-10 2:10 ` Joakim Zhang
2021-05-17 7:53 ` Thierry Reding
2021-05-18 7:52 ` Joakim Zhang
2021-04-22 16:12 ` Florian Fainelli
2021-04-22 17:00 ` Jon Hunter
2021-04-22 17:32 ` Florian Fainelli
2021-04-22 18:18 ` Jon Hunter
2021-04-22 18:20 ` Florian Fainelli
2021-04-23 13:46 ` Jon Hunter
2021-04-23 15:38 ` Heiner Kallweit
2021-04-23 2:37 ` Joakim Zhang
2021-04-22 16:31 ` Florian Fainelli
2021-04-23 2:17 ` Joakim Zhang
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=DB8PR04MB67952FC590FEE5A327DA4C95E6589@DB8PR04MB6795.eurprd04.prod.outlook.com \
--to=qiangqing.zhang@nxp.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=joabreu@synopsys.com \
--cc=jonathanh@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-imx@nxp.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=treding@nvidia.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).