linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: linux-ext4@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>, Jan Kara <jack@suse.cz>
Subject: [PATCH] ext4/super.c: Fix error in ext4_fill_super: ext3_fs_type undeclared (first use in this function)
Date: Wed, 24 Mar 2010 12:45:27 +0100	[thread overview]
Message-ID: <2d0a357f1003240445y27e9e56ete60d0786f42ac486@mail.gmail.com> (raw)

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

Not sure if this is really fixing the problem in [1].

--
Sedat

[1] http://marc.info/?l=linux-ext4&m=126942870916446&w=2

[-- Attachment #2: 0001-ext4-super.c-Fix-error-in-ext4_fill_super-ext3_fs_ty.patch --]
[-- Type: text/x-diff, Size: 922 bytes --]

From 722b3ac46df769e5e759b6f824982d34e14037b4 Mon Sep 17 00:00:00 2001
From: Sedat Dilek <sedat.dilek@gmail.com>
Date: Wed, 24 Mar 2010 12:22:34 +0100
Subject: [PATCH] ext4/super.c: Fix error in ext4_fill_super: ext3_fs_type undeclared (first use in this function)

---
 fs/ext4/super.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 1dbb37a..2dacc82 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -2550,7 +2550,9 @@ static int ext4_fill_super(struct super_block *sb, void *data, int silent)
 	 * enable delayed allocation by default
 	 * Use -o nodelalloc to turn it off
 	 */
+#if !defined(CONFIG_EXT3_FS) && !defined(CONFIG_EXT3_FS_MODULE) && defined(CONFIG_EXT4_USE_FOR_EXT23)	
 	if (sb->s_bdev->bd_holder != &ext3_fs_type)
+#endif
 		set_opt(sbi->s_mount_opt, DELALLOC);
 
 	if (!parse_options((char *) data, sb, &journal_devnum,
-- 
1.7.0.3


             reply	other threads:[~2010-03-24 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 11:45 Sedat Dilek [this message]
2010-03-24 16:13 ` [PATCH] ext4/super.c: Fix error in ext4_fill_super: ext3_fs_type undeclared (first use in this function) tytso
2010-03-24 16:59   ` Sedat Dilek

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=2d0a357f1003240445y27e9e56ete60d0786f42ac486@mail.gmail.com \
    --to=sedat.dilek@googlemail.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).