From: Andrew Lunn <andrew@lunn.ch>
To: Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: David Miller <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"frieder.schrempf@kontron.de" <frieder.schrempf@kontron.de>,
"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: Wed, 16 Jun 2021 15:06:17 +0200 [thread overview]
Message-ID: <YMn3Sd65rzvKasEb@lunn.ch> (raw)
In-Reply-To: <DB8PR04MB6795A2A1D51D95E996B7B75FE60F9@DB8PR04MB6795.eurprd04.prod.outlook.com>
> I try below build options, also can't reproduce this issue, so really don't know how to fix it.
>
> make ARCH=arm64 distclean
> make ARCH=arm64 allmodconfig
> make -j8 ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- W=1 / make -j8 ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- W=2 / make -j8 ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- W=3
>
> I saw many unrelated warnings...
Then it could be sparse. Install sparse and use C=1.
Andrew
next prev parent reply other threads:[~2021-06-16 13:06 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
2021-06-15 12:27 ` Andrew Lunn
2021-06-16 8:28 ` Joakim Zhang
2021-06-16 13:06 ` Andrew Lunn [this message]
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=YMn3Sd65rzvKasEb@lunn.ch \
--to=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 \
--cc=qiangqing.zhang@nxp.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).