Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754632AbZGAMRx (ORCPT ); Wed, 1 Jul 2009 08:17:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751557AbZGAMRq (ORCPT ); Wed, 1 Jul 2009 08:17:46 -0400 Received: from hera.kernel.org ([140.211.167.34]:35135 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750963AbZGAMRq (ORCPT ); Wed, 1 Jul 2009 08:17:46 -0400 Subject: [PATCH -tip RESEND] x86: amd_iommu.c device_nb should be static From: Jaswinder Singh Rajput To: Ingo Molnar , Joerg Roedel , x86 maintainers , LKML Content-Type: text/plain Date: Wed, 01 Jul 2009 17:47:07 +0530 Message-Id: <1246450627.6940.6.camel@hpdv5.satnam> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 (2.24.5-1.fc10) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1336 Lines: 46 device_nb is used only by same file, it should be static. Also fixed NULL pointer issue. Fixed following sparse warnings : arch/x86/kernel/amd_iommu.c:1195:23: warning: symbol 'device_nb' was not declared. Should it be static? arch/x86/kernel/amd_iommu.c:1766:10: warning: Using plain integer as NULL pointer Signed-off-by: Jaswinder Singh Rajput --- arch/x86/kernel/amd_iommu.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/kernel/amd_iommu.c b/arch/x86/kernel/amd_iommu.c index 9372f04..6c99f50 100644 --- a/arch/x86/kernel/amd_iommu.c +++ b/arch/x86/kernel/amd_iommu.c @@ -1192,7 +1192,7 @@ out: return 0; } -struct notifier_block device_nb = { +static struct notifier_block device_nb = { .notifier_call = device_change_notifier, }; @@ -1763,7 +1763,7 @@ static void *alloc_coherent(struct device *dev, size_t size, flag |= __GFP_ZERO; virt_addr = (void *)__get_free_pages(flag, get_order(size)); if (!virt_addr) - return 0; + return NULL; paddr = virt_to_phys(virt_addr); -- 1.6.0.6 -- 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/