From: Jakub Kicinski <kuba@kernel.org>
To: Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
"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, 22 Apr 2021 08:56:48 -0700 [thread overview]
Message-ID: <20210422085648.33738d1f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <DB8PR04MB67953A499438FF3FF6BE531BE6469@DB8PR04MB6795.eurprd04.prod.outlook.com>
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.
next prev parent reply other threads:[~2021-04-22 15:56 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 [this message]
2021-04-23 13:48 ` Jon Hunter
2021-05-06 6:33 ` Joakim Zhang
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=20210422085648.33738d1f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--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=linux-imx@nxp.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=qiangqing.zhang@nxp.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).