From: Nick Warne <nick@ukfsn.org>
To: LKML <linux-kernel@vger.kernel.org>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] EXT4: super.c - remove extraneous newline
Date: Thu, 25 Dec 2008 08:11:20 +0000 [thread overview]
Message-ID: <20081225081120.3100c23e@sauron.linicks.net> (raw)
In-Reply-To: <20081225080647.6890d867@sauron.linicks.net>
On Thu, 25 Dec 2008 08:06:47 +0000
Nick Warne <nick@ukfsn.org> wrote:
> Sorry, I just realised I forgot to finish typing the correct subject
> line in my earlier mail :-) Please ignore earlier mail with the same
> patch.
>
> Applies to stable 2.6.28.
>
> Remove extraneous newline that creates empty print line
> in boot logs.
>
> Signed-off-by: Nick Warne <nick@ukfsn.org>
>
> --- linux-2.6.28/fs/ext4/super.cORIG 2008-12-25
> 01:35:49.156527726 +0000 +++ linux-2.6.28/fs/ext4/super.c
> 2008-12-25 01:36:50.914527855 +0000 @@ -1973,7 +1973,7 @@
> else
> ext4_warning(sb, __func__,
> "extents feature not enabled on this
> filesystem, "
> - "use tune2fs.\n");
> + "use tune2fs.");
>
> /*
> * enable delayed allocation by default
>
Sigh... this is mangled. Sorry for the noise :-(
Applies to stable 2.6.28.
Remove extraneous newline that creates empty print line
in boot logs.
Signed-off-by: Nick Warne <nick@ukfsn.org>
--- linux-2.6.28/fs/ext4/super.cORIG 2008-12-25 01:35:49.156527726 +0000
+++ linux-2.6.28/fs/ext4/super.c 2008-12-25 01:36:50.914527855 +0000
@@ -1973,7 +1973,7 @@
else
ext4_warning(sb, __func__,
"extents feature not enabled on this filesystem, "
- "use tune2fs.\n");
+ "use tune2fs.");
/*
* enable delayed allocation by default
--
Free Software Foundation Associate Member 5508
http://linicks.net/
next prev parent reply other threads:[~2008-12-25 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 8:06 Nick Warne
2008-12-25 8:11 ` Nick Warne [this message]
2009-01-02 4:02 ` Theodore Tso
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=20081225081120.3100c23e@sauron.linicks.net \
--to=nick@ukfsn.org \
--cc=linux-ext4@vger.kernel.org \
--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
Powered by JetHome