From: Joakim Zhang <qiangqing.zhang@nxp.com>
To: David Miller <davem@davemloft.net>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
"frieder.schrempf@kontron.de" <frieder.schrempf@kontron.de>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH V2 net-next 0/2] net: fec: fix TX bandwidth fluctuations
Date: Tue, 15 Jun 2021 06:46:34 +0000 [thread overview]
Message-ID: <DB8PR04MB679518CF771FEBE118E395A3E6309@DB8PR04MB6795.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210611.132514.1451796354248475314.davem@davemloft.net>
Hi David,
> -----Original Message-----
> From: David Miller <davem@davemloft.net>
> Sent: 2021年6月12日 4:25
> To: Joakim Zhang <qiangqing.zhang@nxp.com>
> Cc: kuba@kernel.org; frieder.schrempf@kontron.de; andrew@lunn.ch;
> netdev@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH V2 net-next 0/2] net: fec: fix TX bandwidth fluctuations
>
> From: Joakim Zhang <qiangqing.zhang@nxp.com>
> Date: Fri, 11 Jun 2021 17:50:03 +0800
>
> > This patch set intends to fix TX bandwidth fluctuations, any feedback would
> be appreciated.
> >
> > ---
> > ChangeLogs:
> > V1: remove RFC tag, RFC discussions please turn to below:
> >
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.ker
> nel.org%2Flkml%2FYK0Ce5YxR2WYbrAo%40lunn.ch%2FT%2F&data=04%7
> C01%7Cqiangqing.zhang%40nxp.com%7C45b786c85a294b3ea9ec08d92d1709
> 0c%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637590399225645
> 759%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI
> iLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CFeL4rNWqNs4Xc
> 2NqtBiQxex4%2FXAUhEXWQreftFhnY4%3D&reserved=0
> > V2: change functions to be static in this patch set. And add the
> > t-b tag.
>
> Please fix these warnings in patch #2:
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchw
> ork.hopto.org%2Fstatic%2Fnipa%2F498729%2F12315211%2Fbuild_allmodconfi
> g_warn%2Fsummary&data=04%7C01%7Cqiangqing.zhang%40nxp.com%
> 7C45b786c85a294b3ea9ec08d92d17090c%7C686ea1d3bc2b4c6fa92cd99c5c30
> 1635%7C0%7C0%7C637590399225645759%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C1000&sdata=eb4Ujx2FKOnu5M41j1RnPLCBoEoGfQiCO%2BO5MzIsXyE
> %3D&reserved=0
I can't reproduce these warnings with " make ARCH=arm64 allmodconfig", could you please show me the command you used? Thanks.
Best Regards,
Joakim Zhang
> Thank you.
next prev parent reply other threads:[~2021-06-15 6:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 9:50 [PATCH V2 net-next 0/2] net: fec: fix TX bandwidth fluctuations Joakim Zhang
2021-06-11 9:50 ` [PATCH V2 1/2] net: fec: add FEC_QUIRK_HAS_MULTI_QUEUES represents i.MX6SX ENET IP Joakim Zhang
2021-06-11 9:50 ` [PATCH V2 2/2] net: fec: add ndo_select_queue to fix TX bandwidth fluctuations Joakim Zhang
2021-06-18 15:11 ` kernel test robot
2021-06-11 20:25 ` [PATCH V2 net-next 0/2] net: fec: " David Miller
2021-06-15 6:46 ` Joakim Zhang [this message]
2021-06-15 12:27 ` Andrew Lunn
2021-06-16 8:28 ` Joakim Zhang
2021-06-16 13:06 ` Andrew Lunn
2021-06-17 11:40 ` Joakim Zhang
2021-06-17 13:04 ` Andrew Lunn
2021-06-18 8:11 ` 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=DB8PR04MB679518CF771FEBE118E395A3E6309@DB8PR04MB6795.eurprd04.prod.outlook.com \
--to=qiangqing.zhang@nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=frieder.schrempf@kontron.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).