From: Mat Martineau <martineau@kernel.org>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: Matthieu Baerts <matttbe@kernel.org>,
kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
wintera@linux.ibm.com, guwen@linux.alibaba.com, kuba@kernel.org,
davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
tonylu@linux.alibaba.com, Paolo Abeni <pabeni@redhat.com>,
edumazet@google.com
Subject: Re: [PATCH net-next v6 3/3] net/smc: Introduce IPPROTO_SMC
Date: Fri, 7 Jun 2024 13:32:50 -0700 (PDT) [thread overview]
Message-ID: <ae0e195a-28d2-039f-6f3e-65161ada47d7@kernel.org> (raw)
In-Reply-To: <e6b66001-f3cb-4367-aeaf-600fbc5f77b2@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
On Sat, 8 Jun 2024, D. Wythe wrote:
> Hi Mat and Matthieu,
>
> Thanks very much for your feedback! The reasons you all have provided are
> already quite convincing.
> In fact, as I mentioned earlier, I actually don't have sufficient grounds to
> insist on 263. It seems it's time for a change. 😉
>
Ok, sounds like a good plan.
> Regarding the new value of IPPROTO_SMC, do you have any recommendations?
> Which one might be better, 256 or 261?
Not sure there's a clear winner. If you use 256 that could be a hint for
the next developer to use 257 for a future IPPROTO, so I slightly prefer
256.
- Mat
next prev parent reply other threads:[~2024-06-07 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 12:56 [PATCH net-next v6 0/3] Introduce IPPROTO_SMC D. Wythe
2024-06-05 12:56 ` [PATCH net-next v6 1/3] net/smc: refactoring initialization of smc sock D. Wythe
2024-06-05 12:56 ` [PATCH net-next v6 2/3] net/smc: expose smc proto operations D. Wythe
2024-06-05 12:56 ` [PATCH net-next v6 3/3] net/smc: Introduce IPPROTO_SMC D. Wythe
2024-06-06 21:22 ` Mat Martineau
2024-06-07 5:09 ` D. Wythe
2024-06-07 14:47 ` Matthieu Baerts
2024-06-07 16:47 ` Mat Martineau
2024-06-07 19:35 ` D. Wythe
2024-06-07 20:32 ` Mat Martineau [this message]
2024-06-06 20:26 ` [PATCH net-next v6 0/3] " 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=ae0e195a-28d2-039f-6f3e-65161ada47d7@kernel.org \
--to=martineau@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@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