[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <936046df-5ed9-49e5-906f-dec64a63f531@redhat.com>
Date: Thu, 15 May 2025 10:04:28 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: chia-yu.chang@...ia-bell-labs.com, horms@...nel.org,
donald.hunter@...il.com, xandfury@...il.com, netdev@...r.kernel.org,
dave.taht@...il.com, jhs@...atatu.com, kuba@...nel.org,
stephen@...workplumber.org, xiyou.wangcong@...il.com, jiri@...nulli.us,
davem@...emloft.net, edumazet@...gle.com, andrew+netdev@...n.ch,
ast@...erby.net, liuhangbin@...il.com, shuah@...nel.org,
linux-kselftest@...r.kernel.org, ij@...nel.org, ncardwell@...gle.com,
koen.de_schepper@...ia-bell-labs.com, g.white@...lelabs.com,
ingemar.s.johansson@...csson.com, mirja.kuehlewind@...csson.com,
cheshire@...le.com, rs.ietf@....at, Jason_Livingood@...cast.com,
vidhi_goel@...le.com
Subject: Re: [PATCH v15 net-next 0/5] DUALPI2 patch
Hi,
On 5/9/25 11:47 PM, chia-yu.chang@...ia-bell-labs.com wrote:
> From: Chia-Yu Chang <chia-yu.chang@...ia-bell-labs.com>
>
> Hello,
>
> Please find the DualPI2 patch v14.
[...]
>
> For more details of DualPI2, please refer IETF RFC9332 (https://datatracker.ietf.org/doc/html/rfc9332).
A couple of process notes I should have mentioned earlier. The cover
letter should be more descriptive WRT the actual series contents and
goal, beyond the changelog itself.
Each patch should contain individual changelog, to help the reviewers.
At this point you don't need to add individual changelog for past
revisions, but for any eventual later one.
Not worth to repost just for the above, but if a new revision will be
needed, please take care.
/P
Powered by blists - more mailing lists