[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <290fc244-e88f-47a3-8dd3-0ec27eb5c60b@app.fastmail.com>
Date: Tue, 24 Jun 2025 19:16:04 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Frank Li" <Frank.li@....com>, "James Clark" <james.clark@...aro.org>
Cc: "Vladimir Oltean" <olteanv@...il.com>, "Mark Brown" <broonie@...nel.org>,
"Vladimir Oltean" <vladimir.oltean@....com>,
"Larisa Grigore" <larisa.grigore@....com>, "Christoph Hellwig" <hch@....de>,
linux-spi@...r.kernel.org, imx@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/6] spi: spi-fsl-dspi: Stub out DMA functions
On Tue, Jun 24, 2025, at 18:29, Frank Li wrote:
> On Tue, Jun 24, 2025 at 11:35:33AM +0100, James Clark wrote:
>> This will allow the build to succeed with !CONFIG_HAS_DMA, either due to
>> a randconfig build test or when the target only uses one of the non-DMA
>
> I supposed you met kbuild error. If yes, can you add kbuild build report
> tags.
Actually I would suggest making it a dependency on CONFIG_DMA_ENGINE
instead of CONFIG_HAS_DMA, since that is the more relevant symbol.
It would also be simpler to enforce this in Kconfig if we only
care about users that use the DMA support.
Arnd
Powered by blists - more mailing lists