From: Colin Ian King <colin.i.king@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>,
Richard Weinberger <richard@nod.at>,
Zhihao Cheng <chengzhihao1@huawei.com>,
Artem Sadovnikov <a.sadovnikov@ispras.ru>,
linux-mtd@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] jffs2: Remove space before newline
Date: Tue, 29 Jul 2025 14:43:27 +0100 [thread overview]
Message-ID: <20250729134327.1935856-1-colin.i.king@gmail.com> (raw)
There are a couple of instances of an extraneous space before a
newline in printk and debug messages. Remove the spaces.
Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
fs/jffs2/erase.c | 2 +-
fs/jffs2/summary.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/jffs2/erase.c b/fs/jffs2/erase.c
index fda9f4d6093f..5b7ddec4217c 100644
--- a/fs/jffs2/erase.c
+++ b/fs/jffs2/erase.c
@@ -252,7 +252,7 @@ static inline void jffs2_remove_node_refs_from_ino_list(struct jffs2_sb_info *c,
D2({
int i=0;
struct jffs2_raw_node_ref *this;
- printk(KERN_DEBUG "After remove_node_refs_from_ino_list: \n");
+ printk(KERN_DEBUG "After remove_node_refs_from_ino_list:\n");
this = ic->nodes;
diff --git a/fs/jffs2/summary.c b/fs/jffs2/summary.c
index d83372d3e1a0..a0c1e8b2a02f 100644
--- a/fs/jffs2/summary.c
+++ b/fs/jffs2/summary.c
@@ -615,7 +615,7 @@ int jffs2_sum_scan_sumnode(struct jffs2_sb_info *c, struct jffs2_eraseblock *jeb
if ( je32_to_cpu(summary->cln_mkr) ) {
- dbg_summary("Summary : CLEANMARKER node \n");
+ dbg_summary("Summary : CLEANMARKER node\n");
ret = jffs2_prealloc_raw_node_refs(c, jeb, 1);
if (ret)
--
2.50.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
reply other threads:[~2025-07-29 13:44 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=20250729134327.1935856-1-colin.i.king@gmail.com \
--to=colin.i.king@gmail.com \
--cc=a.sadovnikov@ispras.ru \
--cc=chengzhihao1@huawei.com \
--cc=dwmw2@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).