[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<PAXPR04MB85102F65E17869C13D45F708880EA@PAXPR04MB8510.eurprd04.prod.outlook.com>
Date: Wed, 10 Sep 2025 03:08:18 +0000
From: Wei Fang <wei.fang@....com>
To: Shenwei Wang <shenwei.wang@....com>
CC: Clark Wang <xiaoning.wang@....com>, Stanislav Fomichev <sdf@...ichev.me>,
"imx@...ts.linux.dev" <imx@...ts.linux.dev>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, dl-linux-imx <linux-imx@....com>, Andrew Lunn
<andrew@...n.ch>, Frank Li <frank.li@....com>, Andrew Lunn
<andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann
<daniel@...earbox.net>, Jesper Dangaard Brouer <hawk@...nel.org>, John
Fastabend <john.fastabend@...il.com>
Subject: RE: [PATCH v6 net-next 1/6] net: fec: use a member variable for
maximum buffer size
> > In the fec driver, I noticed that the expression "#if defined
> > (CONFIG_M523x) ||
> > defined(CONFIG_M527x) || ..." is used in four different places. I
> > think we could add a separate patch to define a new macro to replace
> > these occurrences. This new macro should be more generic than
> OPT_ARCH_HAS_MAX_FL.
> >
>
> That is outside the scope of this patch and should be addressed in a follow-up
> cleanup patch later.
>
Okay, make sense.
Powered by blists - more mailing lists