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/2] Minor cleanups in common/rc
Date: Thu, 6 Mar 2025 08:17:39 +0000 [thread overview]
Message-ID: <cover.1741248214.git.nirjhar.roy.lists@gmail.com> (raw)
This patch series removes some unnecessary sourcing of common/rc
and decouples the call to init_rc() from the sourcing of common/rc.
The individual patches have the details. This is proposed in [1] and [2].
[1] https://lore.kernel.org/all/20250206155251.GA21787@frogsfrogsfrogs/
[2] https://lore.kernel.org/all/20250210142322.tptpphdntglsz4eq@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com/
Nirjhar Roy (IBM) (2):
generic/749: Remove redundant sourcing of common/rc
check,common/{preamble,rc},soak: Decoupling init_rc() call from
sourcing common/rc
check | 10 ++--------
common/preamble | 1 +
common/rc | 2 --
soak | 1 +
tests/generic/749 | 1 -
5 files changed, 4 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2025-03-06 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 8:17 Nirjhar Roy (IBM) [this message]
2025-03-06 8:17 ` [PATCH v1 1/2] generic/749: Remove redundant sourcing of common/rc Nirjhar Roy (IBM)
2025-03-06 17:41 ` Darrick J. Wong
2025-03-06 8:17 ` [PATCH v1 2/2] check,common/{preamble,rc},soak: Decoupling init_rc() call from sourcing common/rc Nirjhar Roy (IBM)
2025-03-06 17:46 ` Darrick J. Wong
2025-03-07 5:51 ` Nirjhar Roy (IBM)
2025-03-07 17:40 ` Darrick J. Wong
2025-03-12 5:46 ` Nirjhar Roy (IBM)
2025-03-18 4:57 ` Nirjhar Roy (IBM)
2025-03-06 21:13 ` Zorro Lang
2025-03-07 5:56 ` Nirjhar Roy (IBM)
2025-03-06 21:30 ` Dave Chinner
2025-03-07 8:05 ` Nirjhar Roy (IBM)
2025-03-08 7:20 ` Zorro Lang
2025-03-10 8:06 ` Zorro Lang
2025-03-12 4:41 ` Nirjhar Roy (IBM)
2025-03-12 4:41 ` Nirjhar Roy (IBM)
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.1741248214.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;
as well as URLs for NNTP newsgroup(s).