From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: rdunlap@infradead.org, linux-kernel@vger.kernel.org
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: [PATCH 02/11] Shebang line was missing,fixed
Date: Tue, 22 Jul 2025 16:46:58 +0530 [thread overview]
Message-ID: <8b1848fb520f4bf101b6c7cc3b45e43e2fd2e658.1753182971.git.unixbhaskar@gmail.com> (raw)
In-Reply-To: <cover.1753182971.git.unixbhaskar@gmail.com>
Added the shebang line at the top of file.
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
Documentation/features/list-arch.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/features/list-arch.sh b/Documentation/features/list-arch.sh
index ac8ff7f6f859..e7124a4c3e8f 100755
--- a/Documentation/features/list-arch.sh
+++ b/Documentation/features/list-arch.sh
@@ -1,3 +1,5 @@
+#!/bin/sh
+
# SPDX-License-Identifier: GPL-2.0
#
# Small script that visualizes the kernel feature support status
--
2.49.1
next prev parent reply other threads:[~2025-07-22 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 11:16 [PATCH 00/11] Various trees,shell files missing the shebang line Bhaskar Chowdhury
2025-07-22 11:16 ` [PATCH 01/11] Shebang line was missing,fixed Bhaskar Chowdhury
2025-07-22 11:16 ` Bhaskar Chowdhury [this message]
2025-07-22 11:16 ` [PATCH 03/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 04/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 05/11] There was a space between bang and shell path,fixed Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 06/11] Shebang line was missing,fixed Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 07/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 08/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 09/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 10/11] " Bhaskar Chowdhury
2025-07-22 11:17 ` [PATCH 11/11] " Bhaskar Chowdhury
2025-07-22 12:09 ` [PATCH 00/11] Various trees,shell files missing the shebang line Theodore Ts'o
2025-07-22 17:10 ` Jonathan Corbet
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=8b1848fb520f4bf101b6c7cc3b45e43e2fd2e658.1753182971.git.unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).