linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: elvo@virgilio.it
To: linux-kernel@vger.kernel.org
Subject: [PATCH] fs/ufs/super.c, kernel 2.4.18-pre8
Date: Tue, 28 May 2002 22:35:35 +0000	[thread overview]
Message-ID: <3CDB32970001ECA0@ims1c.cp.tin.it> (raw)

hi all,

there's a little compilation error concerning commas
in the fs/ufs/super.c code, a little patch follows.

elv


ufs_read_super.diff:

--- /root/super.c       Mon May 27 17:42:22 2002
+++ super.c     Mon May 27 17:43:09 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;
        }

// EOF




                 reply	other threads:[~2002-05-28 22:35 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=3CDB32970001ECA0@ims1c.cp.tin.it \
    --to=elvo@virgilio.it \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] fs/ufs/super.c, kernel 2.4.18-pre8' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox