From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 513B2291A for ; Mon, 23 Oct 2023 05:50:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=none Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F2B0FFC for ; Sun, 22 Oct 2023 22:50:52 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 6B12A68AA6; Mon, 23 Oct 2023 07:50:48 +0200 (CEST) Date: Mon, 23 Oct 2023 07:50:48 +0200 From: Christoph Hellwig To: Geert Uytterhoeven Cc: Christoph Hellwig , Greg Ungerer , iommu@lists.linux.dev, Robin Murphy , Marek Szyprowski , Wei Fang , Shenwei Wang , Clark Wang , NXP Linux Team , linux-m68k@lists.linux-m68k.org, netdev@vger.kernel.org, Lad Prabhakar Subject: Re: [PATCH 1/8] dma-direct: add depdenencies to CONFIG_DMA_GLOBAL_POOL Message-ID: <20231023055048.GA11374@lst.de> References: <20231020054024.78295-1-hch@lst.de> <20231020054024.78295-2-hch@lst.de> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) 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 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.