From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
ritesh.list@gmail.com, ojaswin@linux.ibm.com, djwong@kernel.org,
zlang@kernel.org, david@fromorbit.com,
nirjhar.roy.lists@gmail.com
Subject: [PATCH v1 0/3] new: Improvements to new script
Date: Tue, 13 May 2025 08:10:09 +0000 [thread overview]
Message-ID: <cover.1747123422.git.nirjhar.roy.lists@gmail.com> (raw)
This series adds a couple of improvements to the "new" script.
Patch-1/3 - Adds an optional name/email id parameter prompt to the new script while creating
a new test file using the "new" file.
Patch 2/3 - Replace "status=0;exit 0" with _exit 0 in the skeleton file in "new".
Patch 3/3 - Add a make command after the skeleton file is created, so that once
the skeleton file is created, it automatically gets added to group.list file. This
will enable the users to directly run the test without having to explicitly run make
on their own.
Nirjhar Roy (IBM) (3):
new: Add a new parameter (name/emailid) in the "new" script
new: Replace "status=0; exit 0" with _exit 0
new: Run make after adding a new test file
new | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2025-05-13 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 8:10 Nirjhar Roy (IBM) [this message]
2025-05-13 8:10 ` [PATCH v1 1/3] new: Add a new parameter (name/emailid) in the "new" script Nirjhar Roy (IBM)
2025-05-14 5:36 ` Zorro Lang
2025-05-14 6:39 ` Nirjhar Roy (IBM)
2025-05-13 8:10 ` [PATCH v1 2/3] new: Replace "status=0; exit 0" with _exit 0 Nirjhar Roy (IBM)
2025-05-14 5:20 ` Zorro Lang
2025-05-13 8:10 ` [PATCH v1 3/3] new: Run make after adding a new test file Nirjhar Roy (IBM)
2025-05-14 5:16 ` Zorro Lang
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=cover.1747123422.git.nirjhar.roy.lists@gmail.com \
--to=nirjhar.roy.lists@gmail.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=zlang@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