From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265925AbUBJO4G (ORCPT ); Tue, 10 Feb 2004 09:56:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265931AbUBJO4G (ORCPT ); Tue, 10 Feb 2004 09:56:06 -0500 Received: from phoenix.infradead.org ([213.86.99.234]:56075 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S265925AbUBJO4C (ORCPT ); Tue, 10 Feb 2004 09:56:02 -0500 Date: Tue, 10 Feb 2004 14:55:58 +0000 From: Christoph Hellwig To: Geert Uytterhoeven Cc: Linus Torvalds , Greg Kroah-Hartman , Kernel Mailing List Subject: Re: dmapool (was: Re: Linux 2.6.3-rc2) Message-ID: <20040210145558.A4684@infradead.org> Mail-Followup-To: Christoph Hellwig , Geert Uytterhoeven , Linus Torvalds , Greg Kroah-Hartman , Kernel Mailing List References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from geert@linux-m68k.org on Tue, Feb 10, 2004 at 03:32:47PM +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 10, 2004 at 03:32:47PM +0100, Geert Uytterhoeven wrote: > This patch seems to fix the problem (all offending platforms include > if CONFIG_PCI only): Umm, no the whole point of the dmapool is that it's not pci-dependent. Just fix your arch to have proper stub dma_ routines. There were at least two headsups during 2.5 and 2.6-test that this will be required.