From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: masahiroy@kernel.org, nathan@kernel.org, nicolas@fjasle.eu,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: [PATCH] scripts: Improve source code readability by eliminating too many slashes
Date: Fri, 15 Mar 2024 08:00:38 +0530 [thread overview]
Message-ID: <20240315023038.4320-1-unixbhaskar@gmail.com> (raw)
I have tried to eliminate the convolution(visual) of forward slashes.
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
scripts/mkcompile_h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/mkcompile_h b/scripts/mkcompile_h
index 2596f78e52ef..d6a7b22d23e3 100755
--- a/scripts/mkcompile_h
+++ b/scripts/mkcompile_h
@@ -6,7 +6,7 @@ CC_VERSION="$2"
LD=$3
if test -z "$KBUILD_BUILD_USER"; then
- LINUX_COMPILE_BY=$(whoami | sed 's/\\/\\\\/')
+ LINUX_COMPILE_BY=$(whoami | sed 's#\\#\\\\#')
else
LINUX_COMPILE_BY=$KBUILD_BUILD_USER
fi
--
2.35.8
reply other threads:[~2024-03-15 2:30 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=20240315023038.4320-1-unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).