public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@mulix.org>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: PATCH: fix "ide_scan_direction defined but not used" in ide.c
Date: Tue, 7 Jan 2003 15:10:02 +0200	[thread overview]
Message-ID: <20030107131002.GI25540@alhambra> (raw)

ide_scan_drection is only used if CONFIG_BLK_DEV_IDEPCI is defined,
giving a compilation warning otherwise. Against 2.5.54-bk. 

# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.974   -> 1.975  
#	   drivers/ide/ide.c	1.48    -> 1.49   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/01/07	mulix@alhambra.mulix.org	1.975
# fix "defined but not used" warning
# --------------------------------------------
#
diff -Nru a/drivers/ide/ide.c b/drivers/ide/ide.c
--- a/drivers/ide/ide.c	Tue Jan  7 14:17:42 2003
+++ b/drivers/ide/ide.c	Tue Jan  7 14:17:42 2003
@@ -179,7 +179,9 @@
 
 spinlock_t ide_lock __cacheline_aligned_in_smp = SPIN_LOCK_UNLOCKED;
 
+#ifdef CONFIG_BLK_DEV_IDEPCI
 static int ide_scan_direction; /* THIS was formerly 2.2.x pci=reverse */
+#endif /* CONFIG_BLK_DEV_IDEPCI */ 
 
 #ifdef CONFIG_IDEDMA_AUTO
 int noautodma = 0;

-- 
Muli Ben-Yehuda

my opinions may seem crazy. But they all make sense. Insane sense, but
sense nontheless. -- Shlomi Fish on #offtopic.


             reply	other threads:[~2003-01-07 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 13:10 Muli Ben-Yehuda [this message]
2003-01-07 16:36 ` PATCH: fix "ide_scan_direction defined but not used" in ide.c Alan Cox
2003-01-07 16:01   ` Muli Ben-Yehuda
2003-01-07 17:20     ` Alan Cox

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=20030107131002.GI25540@alhambra \
    --to=mulix@mulix.org \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    /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