From: Jakub Kicinski <kuba@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,
horms@kernel.org, linux-rdma@vger.kernel.org,
allison.henderson@oracle.com
Subject: Re: [PATCH net-next v4 8/8] net/rds: Trigger rds_send_ping() more than once
Date: Mon, 2 Feb 2026 17:55:18 -0800 [thread overview]
Message-ID: <20260202175518.3b207c5e@kernel.org> (raw)
In-Reply-To: <20260131012507.814119-9-achender@kernel.org>
On Fri, 30 Jan 2026 18:25:07 -0700 Allison Henderson wrote:
> From: Original Author <email@example.com>
Hi Allison, just noticed this From, I think you'll need to respin.
--
pw-bot: cr
next prev parent reply other threads:[~2026-02-03 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 1:24 [PATCH net-next v4 0/8] net/rds: RDS-TCP protocol and extension improvements Allison Henderson
2026-01-31 1:25 ` [PATCH net-next v4 1/8] net/rds: new extension header: rdma bytes Allison Henderson
2026-01-31 1:25 ` [PATCH net-next v4 2/8] net/rds: Encode cp_index in TCP source port Allison Henderson
2026-01-31 1:25 ` [PATCH net-next v4 3/8] net/rds: rds_tcp_conn_path_shutdown must not discard messages Allison Henderson
2026-01-31 1:25 ` [PATCH net-next v4 4/8] net/rds: Kick-start TCP receiver after accept Allison Henderson
2026-01-31 1:25 ` [PATCH net-next v4 5/8] net/rds: Clear reconnect pending bit Allison Henderson
2026-01-31 1:25 ` [PATCH net-next v4 6/8] net/rds: Update struct rds_statistics to use u64 instead of uint64_t Allison Henderson
2026-01-31 1:25 ` [PATCH net-next v4 7/8] net/rds: Use the first lane until RDS_EXTHDR_NPATHS arrives Allison Henderson
2026-01-31 1:25 ` [PATCH net-next v4 8/8] net/rds: Trigger rds_send_ping() more than once Allison Henderson
2026-02-03 1:55 ` Jakub Kicinski [this message]
2026-02-03 6:41 ` 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=20260202175518.3b207c5e@kernel.org \
--to=kuba@kernel.org \
--cc=achender@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=edumazet@google.com \
--cc=horms@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