From: Jakub Kicinski <kuba@kernel.org>
To: wenjia@linux.ibm.com, jaka@linux.ibm.com
Cc: Guangguan Wang <guangguan.wang@linux.alibaba.com>,
alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
linux-rdma@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net/smc: Two features for smc-r
Date: Wed, 4 Dec 2024 18:39:45 -0800 [thread overview]
Message-ID: <20241204183945.47759ac5@kernel.org> (raw)
In-Reply-To: <20241202125203.48821-1-guangguan.wang@linux.alibaba.com>
On Mon, 2 Dec 2024 20:52:01 +0800 Guangguan Wang wrote:
> net/smc: Two features for smc-r
changes look relatively straightforward, IBM folks do you need more
time to review?
next prev parent reply other threads:[~2024-12-05 2:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 12:52 [PATCH net-next v2 0/2] net/smc: Two features for smc-r Guangguan Wang
2024-12-02 12:52 ` [PATCH net-next v2 1/2] net/smc: support SMC-R V2 for rdma devices with max_recv_sge equals to 1 Guangguan Wang
2024-12-06 19:12 ` Wenjia Zhang
2024-12-02 12:52 ` [PATCH net-next v2 2/2] net/smc: support ipv4 mapped ipv6 addr client for smc-r v2 Guangguan Wang
2024-12-05 10:16 ` Wenjia Zhang
2024-12-05 12:02 ` Guangguan Wang
2024-12-05 12:58 ` Halil Pasic
2024-12-06 6:06 ` Guangguan Wang
2024-12-06 10:51 ` Wenjia Zhang
2024-12-06 19:49 ` Wenjia Zhang
2024-12-09 6:04 ` Guangguan Wang
2024-12-09 8:49 ` Wenjia Zhang
2024-12-09 9:46 ` Halil Pasic
2024-12-09 12:36 ` Guangguan Wang
2024-12-09 20:44 ` Halil Pasic
2024-12-10 7:07 ` Guangguan Wang
2024-12-10 9:59 ` Halil Pasic
2024-12-05 2:39 ` Jakub Kicinski [this message]
2024-12-05 7:27 ` [PATCH net-next v2 0/2] net/smc: Two features for smc-r Wenjia Zhang
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=20241204183945.47759ac5@kernel.org \
--to=kuba@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guangguan.wang@linux.alibaba.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=jaka@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).