Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752545AbYGIHj0 (ORCPT ); Wed, 9 Jul 2008 03:39:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756106AbYGIHjE (ORCPT ); Wed, 9 Jul 2008 03:39:04 -0400 Received: from mfo10.iij4u.or.jp ([210.138.174.80]:49524 "EHLO mfo10.iij4u.or.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753628AbYGIHjD (ORCPT ); Wed, 9 Jul 2008 03:39:03 -0400 X-Greylist: delayed 552 seconds by postgrey-1.27 at vger.kernel.org; Wed, 09 Jul 2008 03:39:03 EDT Date: Wed, 9 Jul 2008 16:29:41 +0900 To: mingo@elte.hu Cc: linux-kernel@vger.kernel.org Subject: [PATCH] replace CONFIG_IOMMU with CONFIG_GART_IOMMU in iommu.h From: FUJITA Tomonori Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20080709162913H.tomof@acm.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1182 Lines: 32 Should be CONFIG_GART_IOMMU instead of CONFIG_IOMMU here? Hmm, looks like it would be nice to have more cleanups of iommu.h and gart.h. This is against tip/master. = From: FUJITA Tomonori Subject: [PATCH] replace CONFIG_IOMMU with CONFIG_GART_IOMMU in iommu.h Signed-off-by: FUJITA Tomonori --- include/asm-x86/iommu.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/asm-x86/iommu.h b/include/asm-x86/iommu.h index 07862fd..cb7e989 100644 --- a/include/asm-x86/iommu.h +++ b/include/asm-x86/iommu.h @@ -5,7 +5,7 @@ extern void pci_iommu_shutdown(void); extern void no_iommu_init(void); extern int force_iommu, no_iommu; extern int iommu_detected; -#ifdef CONFIG_IOMMU +#ifdef CONFIG_GART_IOMMU extern void gart_iommu_init(void); extern void gart_iommu_shutdown(void); extern void __init gart_parse_options(char *); -- 1.5.4.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/