From: Marc-Christian Petersen <mcp@linux-systeme.de>
To: linux-kernel@vger.kernel.org
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: [PATCH] 2.4.19-pre8 UFS Compile Fix
Date: Mon, 20 May 2002 03:49:23 +0200 [thread overview]
Message-ID: <200205200346.06521.mcp@linux-systeme.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Hi all,
UFS isn't buildable with 2.4.19-pre8.
Patch is attached, fixes missing 4 commas.
This is also CC'ed to Marcello.
If this was reported before, i don't get it.
--
Kind regards
Marc-Christian Petersen
http://sourceforge.net/projects/wolk
PGP/GnuPG Key: 1024D/408B2D54947750EC
Fingerprint: 8602 69E0 A9C2 A509 8661 2B0B 408B 2D54 9477 50EC
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
[-- Attachment #2: ufs-compile-fix.patch --]
[-- Type: text/x-diff, Size: 983 bytes --]
--- linux-jp12/fs/ufs/super.c Wed May 15 00:27:01 2002
+++ linux/fs/ufs/super.c Mon May 20 00:32:22 2002
@@ -663,12 +663,12 @@
goto failed;
}
if (uspi->s_bsize < 512) {
- printk("ufs_read_super: fragment size %u is too small\n"
+ printk("ufs_read_super: fragment size %u is too small\n",
uspi->s_fsize);
goto failed;
}
if (uspi->s_bsize > 4096) {
- printk("ufs_read_super: fragment size %u is too large\n"
+ printk("ufs_read_super: fragment size %u is too large\n",
uspi->s_fsize);
goto failed;
}
@@ -678,12 +678,12 @@
goto failed;
}
if (uspi->s_bsize < 4096) {
- printk("ufs_read_super: block size %u is too small\n"
+ printk("ufs_read_super: block size %u is too small\n",
uspi->s_fsize);
goto failed;
}
if (uspi->s_bsize / uspi->s_fsize > 8) {
- printk("ufs_read_super: too many fragments per block (%u)\n"
+ printk("ufs_read_super: too many fragments per block (%u)\n",
uspi->s_bsize / uspi->s_fsize);
goto failed;
}
next reply other threads:[~2002-05-20 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 1:49 Marc-Christian Petersen [this message]
2002-05-20 14:43 ` [PATCH] 2.4.19-pre8 UFS Compile Fix Måns Rullgård
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=200205200346.06521.mcp@linux-systeme.de \
--to=mcp@linux-systeme.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.