mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Trivial Russell <trivial@rustcorp.com.au>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [TRIVIAL] eliminate warnings in mtrr_if.c when !CONFIG_PROC_FS
Date: Thu, 04 Sep 2003 13:26:13 +1000	[thread overview]
Message-ID: <20030904033019.3E4342C225@lists.samba.org> (raw)

From:  Stephen Hemminger <shemminger@osdl.org>

  Patch against 2.6.0-test1 latest (post-bk2).  Get's rid of unused variable and function
  warnings if /proc is not configured on.

--- trivial-2.6.0-test4-bk5/arch/i386/kernel/cpu/mtrr/if.c.orig	2003-09-04 13:02:00.000000000 +1000
+++ trivial-2.6.0-test4-bk5/arch/i386/kernel/cpu/mtrr/if.c	2003-09-04 13:02:00.000000000 +1000
@@ -13,6 +13,7 @@
 /* RED-PEN: this is accessed without any locking */
 extern unsigned int *usage_table;
 
+#ifdef CONFIG_PROC_FS
 static int mtrr_seq_show(struct seq_file *seq, void *offset);
 
 #define FILE_FCOUNT(f) (((struct seq_file *)((f)->private_data))->private)
@@ -310,11 +311,9 @@
 	.release = mtrr_close,
 };
 
-#  ifdef CONFIG_PROC_FS
 
 static struct proc_dir_entry *proc_root_mtrr;
 
-#  endif			/*  CONFIG_PROC_FS  */
 
 static int mtrr_seq_show(struct seq_file *seq, void *offset)
 {
@@ -349,6 +348,8 @@
 	return 0;
 }
 
+#  endif			/*  CONFIG_PROC_FS  */
+
 static int __init mtrr_if_init(void)
 {
 #ifdef CONFIG_PROC_FS
-- 
  What is this? http://www.kernel.org/pub/linux/kernel/people/rusty/trivial/
  Don't blame me: the Monkey is driving
  File: Stephen Hemminger <shemminger@osdl.org>: [PATCH] eliminate warnings in mtrr_if.c when !CONFIG_PROC_FS

                 reply	other threads:[~2003-09-04  3:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030904033019.3E4342C225@lists.samba.org \
    --to=trivial@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®