From: Jakub Kicinski <kuba@kernel.org>
To: Chuyf26 <Chuyf26@linux.alibaba.com>
Cc: pabeni@redhat.com, alibuda@linux.alibaba.com,
dust.li@linux.ibm.com, sidraya@linux.ibm.com,
mjambigi@linux.ibm.com, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v3] net/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure
Date: Fri, 21 Aug 2026 16:53:38 -0700 [thread overview]
Message-ID: <20260821165338.21c8d11d@kernel.org> (raw)
In-Reply-To: <178729790329.223882.15209084993558811810@linux.alibaba.com>
On Fri, 21 Aug 2026 15:38:23 +0800 Chuyf26 wrote:
> Signed-off-by: Chuyf26 <Chuyf26@linux.alibaba.com>
We need something more official-name like for the author
and the sign off. The numbers do not look right/
It'd also be great if you paid attention to the automated
emails you're receiving telling to not post new patches
in reply to the old ones
--
pw-bot: cr
next prev parent reply other threads:[~2026-08-21 23:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260812071543.C94FD349CD8@smtp.subspace.kernel.org>
2026-08-12 14:44 ` [PATCH] net/smc: release the internal TCP sock on IPPROTO_SMC socket creation failure Sidraya Jayagond
2026-08-13 6:04 ` [PATCH v2] " Chuyf26
2026-08-13 6:14 ` sashiko-bot
2026-08-20 11:12 ` Paolo Abeni
2026-08-21 7:38 ` [PATCH v3] " Chuyf26
2026-08-21 23:53 ` Jakub Kicinski [this message]
2026-08-22 7:40 ` sashiko-bot
[not found] ` <202608130604.67D5j4VU1508130@pps.reinject>
2026-08-13 6:25 ` [PATCH v2] " Sidraya Jayagond
2026-08-12 7:15 [PATCH] " Chuyf26
2026-08-12 7:25 ` sashiko-bot
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=20260821165338.21c8d11d@kernel.org \
--to=kuba@kernel.org \
--cc=Chuyf26@linux.alibaba.com \
--cc=alibuda@linux.alibaba.com \
--cc=dust.li@linux.ibm.com \
--cc=guwen@linux.alibaba.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.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.