public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Ouellette <ouellettes@videotron.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH]   Unused variable warning in fs/ext3/super.c if CONFIG_QUOTA is not defined
Date: Fri, 08 Aug 2003 23:57:41 -0400	[thread overview]
Message-ID: <3F347135.8070900@videotron.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 198 bytes --]

Folks,

    the following two patches fix a compile warning in fs/ext3/super.c 
if CONFIG_QUOTA is not defined.

    The patches apply against 2.4.22-rc1-ac1  and  2.6.0-test2.

Stephane Ouellette


[-- Attachment #2: super.c-2.4.22-rc1-ac1.diff --]
[-- Type: text/plain, Size: 389 bytes --]

--- linux-2.4.22-rc1-ac1-orig/fs/ext3/super.c	Fri Aug  8 22:34:32 2003
+++ linux-2.4.22-rc1-ac1-fixed/fs/ext3/super.c	Fri Aug  8 23:48:54 2003
@@ -449,7 +449,10 @@
 }
 
 static struct dquot_operations ext3_qops;
+
+#ifdef CONFIG_QUOTA
 static int (*old_sync_dquot)(struct dquot *dquot);
+#endif
 
 static struct super_operations ext3_sops = {
 	read_inode:	ext3_read_inode,	/* BKL held */

[-- Attachment #3: super.c-2.6.0-test2.diff --]
[-- Type: text/plain, Size: 467 bytes --]

--- linux-2.6.0-test2-orig/fs/ext3/super.c	2003-07-27 13:09:04.000000000 -0400
+++ linux-2.6.0-test2-fixed/fs/ext3/super.c	2003-08-08 23:52:42.000000000 -0400
@@ -2000,7 +2000,9 @@
 /* Blocks: quota info + (4 pointer blocks + 1 entry block) * (3 indirect + 1 descriptor + 1 bitmap) + superblock */
 #define EXT3_V0_QFMT_BLOCKS 27
 
+#ifdef CONFIG_QUOTA
 static int (*old_sync_dquot)(struct dquot *dquot);
+#endif
 
 static int ext3_sync_dquot(struct dquot *dquot)
 {

                 reply	other threads:[~2003-08-09  3:57 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=3F347135.8070900@videotron.ca \
    --to=ouellettes@videotron.ca \
    --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