[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250829142636.7nv3ylyck5yda3fd@skbuf>
Date: Fri, 29 Aug 2025 17:26:36 +0300
From: Vladimir Oltean <vladimir.oltean@....com>
To: James Clark <james.clark@...aro.org>
Cc: Vladimir Oltean <olteanv@...il.com>, Mark Brown <broonie@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
Larisa Grigore <larisa.grigore@....com>,
Frank Li <Frank.li@....com>, Christoph Hellwig <hch@....de>,
linux-spi@...r.kernel.org, imx@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 3/7] spi: spi-fsl-dspi: Stub out DMA functions
Hi James,
On Fri, Aug 29, 2025 at 12:46:45PM +0100, James Clark wrote:
> This will allow the build to succeed with !CONFIG_DMA_ENGINE, either due
> to a randconfig build test or when the target only uses one of the
> non-DMA transfer modes which this driver supports.
>
> Signed-off-by: James Clark <james.clark@...aro.org>
> ---
Sorry for not paying attention to this previously. I didn't pick up from
previous conversations what problem this is addressing. I built an arm64
kernel with CONFIG_DMA_ENGINE disabled (by unsetting CONFIG_DMADEVICES)
and it got built successfully. The .config is attached.
Please post the specific build error if you haven't done so already, and
give a reasonable hint at the technical motivation in the commit message.
View attachment ".config" of type "text/plain" (362945 bytes)
Powered by blists - more mailing lists