From: Allison Henderson <achender@kernel.org>
To: netdev@vger.kernel.org
Cc: linux-kselftest@vger.kernel.org, pabeni@redhat.com,
edumazet@google.com, rds-devel@oss.oracle.com, kuba@kernel.org,
shuah@kernel.org, horms@kernel.org, linux-rdma@vger.kernel.org,
allison.henderson@oracle.com
Subject: [PATCH net-next v3 0/2] selftests: rds: add config file and config.sh -c option
Date: Thu, 19 Mar 2026 21:18:32 -0700 [thread overview]
Message-ID: <20260320041834.2761069-1-achender@kernel.org> (raw)
This series adds an RDS-specific config file for ksft CI and extends
config.sh with a -c flag to specify an alternate config file path.
Users can now specify the path of the config they want to update, or
default to .config if none is specified.
---
Changes v2 -> v3:
[PATCH net-next v3 1/2] selftests: rds: add tools/testing/selftests/net/rds/config
- Sort CONFIG entries in tools/testing/selftests/net/rds/config
- Sort TEST_FILES entries alphabetically in Makefile
[PATCH net-next v3 2/2] selftests: rds: Add -c config option to rds/config.sh
- Use bash array for FLAGS to keep config.sh shellcheck clean
Allison Henderson (2):
selftests: rds: add tools/testing/selftests/net/rds/config
selftests: rds: Add -c config option to rds/config.sh
tools/testing/selftests/net/rds/Makefile | 1 +
tools/testing/selftests/net/rds/README.txt | 5 ++-
tools/testing/selftests/net/rds/config | 5 +++
tools/testing/selftests/net/rds/config.sh | 37 +++++++++++++---------
4 files changed, 32 insertions(+), 16 deletions(-)
create mode 100644 tools/testing/selftests/net/rds/config
--
2.43.0
next reply other threads:[~2026-03-20 4:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 4:18 Allison Henderson [this message]
2026-03-20 4:18 ` [PATCH net-next v3 1/2] selftests: rds: add tools/testing/selftests/net/rds/config Allison Henderson
2026-03-24 2:40 ` Jakub Kicinski
2026-03-24 6:29 ` Allison Henderson
2026-03-20 4:18 ` [PATCH net-next v3 2/2] selftests: rds: Add -c config option to rds/config.sh Allison Henderson
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=20260320041834.2761069-1-achender@kernel.org \
--to=achender@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.