mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Colin Ian King <colin.i.king@gmail.com>
To: Mike Marshall <hubcap@omnibond.com>,
	Martin Brandenburg <martin@omnibond.com>,
	devel@lists.orangefs.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] orangefs: Remove space before newline
Date: Tue, 29 Jul 2025 14:35:10 +0100	[thread overview]
Message-ID: <20250729133510.1934993-1-colin.i.king@gmail.com> (raw)

There are a couple of instances of an extraneous space before a
newline in gossip_* messages. Remove the spaces.

Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
 fs/orangefs/inode.c            | 2 +-
 fs/orangefs/orangefs-debugfs.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/orangefs/inode.c b/fs/orangefs/inode.c
index a01400cd41fd..ac1469a0d663 100644
--- a/fs/orangefs/inode.c
+++ b/fs/orangefs/inode.c
@@ -246,7 +246,7 @@ static void orangefs_readahead(struct readahead_control *rac)
 			&offset, &iter, readahead_length(rac),
 			inode->i_size, NULL, NULL, rac->file)) < 0)
 		gossip_debug(GOSSIP_FILE_DEBUG,
-			"%s: wait_for_direct_io failed. \n", __func__);
+			"%s: wait_for_direct_io failed.\n", __func__);
 	else
 		ret = 0;
 
diff --git a/fs/orangefs/orangefs-debugfs.c b/fs/orangefs/orangefs-debugfs.c
index 1c375fb65018..4582f53bb2d8 100644
--- a/fs/orangefs/orangefs-debugfs.c
+++ b/fs/orangefs/orangefs-debugfs.c
@@ -985,7 +985,7 @@ int orangefs_debugfs_new_client_string(void __user *arg)
 		/* Build a proper debug help string. */
 		ret = orangefs_prepare_debugfs_help_string(0);
 		if (ret) {
-			gossip_err("%s: no debug help string \n",
+			gossip_err("%s: no debug help string\n",
 				   __func__);
 			return ret;
 		}
-- 
2.50.0


                 reply	other threads:[~2025-07-29 13: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=20250729133510.1934993-1-colin.i.king@gmail.com \
    --to=colin.i.king@gmail.com \
    --cc=devel@lists.orangefs.org \
    --cc=hubcap@omnibond.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@omnibond.com \
    /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

all inboxes | Powered by JetHome®