From: syzbot <syzbot@syzkaller.appspotmail.com>
To: syzbot@lists.linux.dev
Cc: syzbot <syzbot+ci858e84e8400d24b3@syzkaller.appspotmail.com>,
allison.henderson@oracle.com
Subject: Forwarded: Re: [syzbot ci] Re: net/rds: RDS-TCP reconnect and fanout improvements
Date: Tue, 10 Feb 2026 00:14:10 -0800 [thread overview]
Message-ID: <698ae8d2.050a0220.3b3015.008e.GAE@google.com> (raw)
In-Reply-To: <54193ab13758d5496be6c8b5de9c32992d79f30b.camel@oracle.com>
For archival purposes, forwarding an incoming command email to
syzbot@lists.linux.dev.
***
Subject: Re: [syzbot ci] Re: net/rds: RDS-TCP reconnect and fanout improvements
Author: allison.henderson@oracle.com
#syz test: https://github.com/allisonhenderson/rds_work.git rds_tcp_bug_fixes_v15
parent reply other threads:[~2026-02-10 8:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <54193ab13758d5496be6c8b5de9c32992d79f30b.camel@oracle.com>]
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=698ae8d2.050a0220.3b3015.008e.GAE@google.com \
--to=syzbot@syzkaller.appspotmail.com \
--cc=allison.henderson@oracle.com \
--cc=syzbot+ci858e84e8400d24b3@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
/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.