From: Simon Horman <horms@kernel.org>
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, rds-devel@oss.oracle.com,
kuba@kernel.org, linux-rdma@vger.kernel.org,
allison.henderson@oracle.com
Subject: Re: [PATCH net-next v2 2/2] selftests: rds: Add -c config option to rds/config.sh
Date: Thu, 19 Mar 2026 20:16:13 +0000 [thread overview]
Message-ID: <20260319201613.GV1753385@horms.kernel.org> (raw)
In-Reply-To: <20260319004618.2577324-3-achender@kernel.org>
On Wed, Mar 18, 2026 at 05:46:18PM -0700, Allison Henderson wrote:
> This patch adds a new -c flag to config.sh that enables callers
> to specify the file path of the config they would like to update.
> If no config is specified, the default will be the .config of the
> current directory.
>
> Signed-off-by: Allison Henderson <achender@kernel.org>
Hi Allison,
Shell checks complains about unquoted variables (SC2086) in this patch.
As the script was previously shellcheck clean it would be nice
to keep it that way.
...
next prev parent reply other threads:[~2026-03-19 20:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 0:46 [PATCH net-next v2 0/2] selftests: rds: add config file and config.sh -c option Allison Henderson
2026-03-19 0:46 ` [PATCH net-next v2 1/2] selftests: rds: add tools/testing/selftests/net/rds/config Allison Henderson
2026-03-19 23:54 ` Jakub Kicinski
2026-03-19 23:55 ` Jakub Kicinski
2026-03-20 3:06 ` Allison Henderson
2026-03-19 0:46 ` [PATCH net-next v2 2/2] selftests: rds: Add -c config option to rds/config.sh Allison Henderson
2026-03-19 20:13 ` [net-next,v2,2/2] " Simon Horman
2026-03-20 3:05 ` Allison Henderson
2026-03-20 8:26 ` Simon Horman
2026-03-19 20:16 ` Simon Horman [this message]
2026-03-20 3:06 ` [PATCH net-next v2 2/2] " 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=20260319201613.GV1753385@horms.kernel.org \
--to=horms@kernel.org \
--cc=achender@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=edumazet@google.com \
--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 \
/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