public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] x86: iommu_sac_force can become static
Date: Mon, 28 Apr 2008 03:15:58 +0400	[thread overview]
Message-ID: <1209338159-30095-2-git-send-email-dmitri.vorobiev@gmail.com> (raw)
In-Reply-To: <1209338159-30095-1-git-send-email-dmitri.vorobiev@gmail.com>

The iommu_sac_force variable is needlessly defined global,
and this patch makes it static. Additionally, this variable
needs not be explicitly initialized.

Signed-off-by: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
---
 arch/x86/kernel/pci-dma.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c
index 50a18e4..81862d0 100644
--- a/arch/x86/kernel/pci-dma.c
+++ b/arch/x86/kernel/pci-dma.c
@@ -14,7 +14,7 @@ EXPORT_SYMBOL(forbid_dac);
 const struct dma_mapping_ops *dma_ops;
 EXPORT_SYMBOL(dma_ops);
 
-int iommu_sac_force __read_mostly = 0;
+static int iommu_sac_force __read_mostly;
 
 #ifdef CONFIG_IOMMU_DEBUG
 int panic_on_overflow __read_mostly = 1;
-- 
1.5.3.6


  reply	other threads:[~2008-04-27 23:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 23:15 x86: fix a couple of sparse warnings Dmitri Vorobiev
2008-04-27 23:15 ` Dmitri Vorobiev [this message]
2008-04-27 23:15 ` [PATCH 2/2] x86: add proper header for reboot_force Dmitri Vorobiev
2008-04-28 12:38 ` x86: fix a couple of sparse warnings Ingo Molnar
2008-04-28 13:37   ` Adrian Bunk
2008-04-28 13:43     ` Dmitri Vorobiev
2008-04-28 13:59       ` Adrian Bunk
2008-04-28 15:01         ` Ingo Molnar
2008-04-28 18:56           ` Adrian Bunk
2008-04-28 19:13             ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1209338159-30095-2-git-send-email-dmitri.vorobiev@gmail.com \
    --to=dmitri.vorobiev@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox