From: Simon Horman <horms@kernel.org>
To: Allison Henderson <allison.henderson@oracle.com>
Cc: "achender@kernel.org" <achender@kernel.org>,
"rds-devel@oss.oracle.com" <rds-devel@oss.oracle.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [net-next,v2,2/2] selftests: rds: Add -c config option to rds/config.sh
Date: Fri, 20 Mar 2026 08:26:08 +0000 [thread overview]
Message-ID: <20260320082608.GZ1753385@horms.kernel.org> (raw)
In-Reply-To: <f0cf57ea9a139ea9af7556442304f8b70d416c16.camel@oracle.com>
On Fri, Mar 20, 2026 at 03:05:22AM +0000, Allison Henderson wrote:
> On Thu, 2026-03-19 at 20:13 +0000, Simon Horman wrote:
> > This is an AI-generated review of your patch. The human sending this
> > email has considered the AI review valid, or at least plausible.
> Alrighty, I will update the README. Thank you!
Thanks.
FWIIW, I do agree the code changes here in v2 are in line with the
discussion around v1.
...
next prev parent reply other threads:[~2026-03-20 8:26 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 [this message]
2026-03-19 20:16 ` [PATCH net-next v2 2/2] " Simon Horman
2026-03-20 3:06 ` 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=20260320082608.GZ1753385@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 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.