[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d62254e-5cbe-4174-95d8-e80cae4f4543@sirena.org.uk>
Date: Mon, 16 Jun 2025 13:11:49 +0100
From: Mark Brown <broonie@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: James Clark <james.clark@...aro.org>, olteanv@...il.com,
oe-kbuild-all@...ts.linux.dev, arnd@...db.de,
larisa.grigore@....com, Frank.li@....com, linux-spi@...r.kernel.org,
imx@...ts.linux.dev, linux-kernel@...r.kernel.org,
kernel test robot <lkp@...el.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Robin Murphy <robin.murphy@....com>, iommu@...ts.linux.dev
Subject: Re: [PATCH] dma-mapping: Stub out dma_{alloc,free,map}_pages() API
On Mon, Jun 16, 2025 at 02:08:32PM +0200, Christoph Hellwig wrote:
> On Mon, Jun 16, 2025 at 01:06:00PM +0100, Mark Brown wrote:
> > The issue with HAS_DMA is that essentially all platforms have and rely
> > on DMA. This ends up just being painful noise from the buildbots when
> > they do randconfigs rather than something useful.
> In most case the driver really does depend on DMA to work, so just
> depend on HAS_DMA. If it can work without DMA, you can use IS_ENABLED.
Right, so you just end up with essentially every driver that isn't
already tied to a platform that needs DMA needing to add the dependency
which nobody is going to notice without doing build testing for
randconfigs or similar non-useful configs - it's not a productive use of
time.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists