linux-kernel - [PATCH -mmotm] cciss: fix build for CONFIG_PROC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100604094137.0702daa1.randy.dunlap@oracle.com>
Date:	Fri, 4 Jun 2010 09:41:37 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	linux-kernel@...r.kernel.org
Cc:	akpm@...ux-foundation.org, Mike Miller <mike.miller@...com>
Subject: [PATCH -mmotm] cciss: fix build for CONFIG_PROC_FS=n

From: Randy Dunlap <randy.dunlap@...cle.com>

Fix build for CONFIG_PROC_FS not enabled; fixes this build error:
drivers/block/cciss.c:3422: error: implicit declaration of function 'next_command'

Looks like the next_command() function was added at a bad location
in cciss-add-performant-mode-support-for-stars-sirius.patch.

Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
Cc: Mike Miller <mike.miller@...com>
---
 drivers/block/cciss.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- mmotm-2010-0603-1636.orig/drivers/block/cciss.c
+++ mmotm-2010-0603-1636/drivers/block/cciss.c
@@ -372,8 +372,6 @@ static const char *raid_label[] = { "0",
 };
 #define RAID_UNKNOWN (sizeof(raid_label) / sizeof(raid_label[0])-1)
 
-#ifdef CONFIG_PROC_FS
-
 static inline u32 next_command(ctlr_info_t *h)
 {
 	u32 a;
@@ -396,6 +394,8 @@ static inline u32 next_command(ctlr_info
 	return a;
 }
 
+#ifdef CONFIG_PROC_FS
+
 /*
  * Report information about this controller.
  */
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/