[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240708133746.ea62kkeq2inzcos5@skbuf>
Date: Mon, 8 Jul 2024 16:37:46 +0300
From: Vladimir Oltean <olteanv@...il.com>
To: Breno Leitao <leitao@...ian.org>
Cc: kernel test robot <lkp@...el.com>, linuxppc-dev@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org, netdev@...r.kernel.org,
llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
kuba@...nel.org, horms@...nel.org, Roy.Pledge@....com,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] soc: fsl: qbman: FSL_DPAA depends on COMPILE_TEST
On Thu, Jun 27, 2024 at 11:40:24AM -0700, Breno Leitao wrote:
> Hello Vladimir,
>
> On Wed, Jun 26, 2024 at 05:06:23PM +0300, Vladimir Oltean wrote:
> > On Wed, Jun 26, 2024 at 08:09:53PM +0800, kernel test robot wrote:
>
> > > All warnings (new ones prefixed by >>):
> > >
> > > >> drivers/net/ethernet/freescale/dpaa/dpaa_eth.c:3280:12: warning: stack frame size (16664) exceeds limit (2048) in 'dpaa_eth_probe' [-Wframe-larger-than]
> > > 3280 | static int dpaa_eth_probe(struct platform_device *pdev)
> > > | ^
> > > 1 warning generated.
> > > --
> > > >> drivers/net/ethernet/freescale/dpaa/dpaa_ethtool.c:454:12: warning: stack frame size (8264) exceeds limit (2048) in 'dpaa_set_coalesce' [-Wframe-larger-than]
> > > 454 | static int dpaa_set_coalesce(struct net_device *dev,
> > > | ^
> > > 1 warning generated.
> >
> > Arrays of NR_CPUS elements are what it probably doesn't like?
>
> Can it use the number of online CPUs instead of NR_CPUS?
I don't see how, given that variable length arrays are something which
should be avoided in the kernel?
Powered by blists - more mailing lists