[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231023055048.GA11374@lst.de>
Date: Mon, 23 Oct 2023 07:50:48 +0200
From: Christoph Hellwig <hch@....de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Christoph Hellwig <hch@....de>, Greg Ungerer <gerg@...ux-m68k.org>,
iommu@...ts.linux.dev, Robin Murphy <robin.murphy@....com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Wei Fang <wei.fang@....com>, Shenwei Wang <shenwei.wang@....com>,
Clark Wang <xiaoning.wang@....com>,
NXP Linux Team <linux-imx@....com>, linux-m68k@...ts.linux-m68k.org,
netdev@...r.kernel.org,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH 1/8] dma-direct: add depdenencies to
CONFIG_DMA_GLOBAL_POOL
On Fri, Oct 20, 2023 at 09:18:32AM +0200, Geert Uytterhoeven wrote:
> s/depdenencies/dependencies/
>
> On Fri, Oct 20, 2023 at 7:40 AM Christoph Hellwig <hch@....de> wrote:
> > CONFIG_DMA_GLOBAL_POOL can't be combined with other DMA coherent
> > allocators. Add dependencies to Kconfig to document this, and make
> > kconfig complain about unment dependencies if someone tries.
>
> unmet
Thanks, I've fixed this up, and also removed the line selecting
ARCH_USE_DMA_ALLOC which snuk back into the second to last patch
after the last rebase and applied the whole series to the dma-mapping
tree now.
The RISC-V dependency fixes still haven't made it to the SOC tree, so
you will see dependency warnings in linux-next until that gets fixed.
Powered by blists - more mailing lists