Re: [PATCH net-next v4 0/2] selftests/net/openvswitch: SCTP tests

[Ilya Maximets <i.maximets@ovn.org>]

On 9/9/26 2:25 PM, Minxi Hou wrote:
> This series extends the Open vSwitch SCTP selftests: patch 1 adds the
> IPv6 flow-key test (mirroring the merged IPv4 test), and patch 2 adds an
> SCTP NAT test exercising port translation across conntrack.
> 
> v3 -> v4:
> - test_sctp_connect_v6 now also asserts that installing a keyless
>   ipv6(proto=132) flow is refused with EINVAL, pinning the reject side
>   of the match_validate() sctp() key requirement (pointed out in
>   review: only the accept side was exercised, so a regression dropping
>   the requirement would have passed unnoticed). The refusal is checked
>   to be errno 22 specifically, not a flow-string parse error.
> - Wrap a few over-80-column lines in the NAT test; checkpatch strict
>   is now clean for the series.
> - Rebased onto 548b86839f7f.
> 
> Signed-off-by: Minxi Hou <houminxi@gmail.com>
> 
> Minxi Hou (2):
>   selftests/net/openvswitch: add SCTP flow key test over IPv6
>   selftests/net/openvswitch: add SCTP NAT test with port translation
> 
>  .../testing/selftests/net/openvswitch/config  |   1 +
>  .../selftests/net/openvswitch/openvswitch.sh  | 201 ++++++++++++++++++
>  2 files changed, 202 insertions(+)
Beside the Aaron's comment on v3, please, avoid re-naming patches and
the series while sending new versions.  This confuses both the automation
and humans trying to follow the history of the change.

Also, keep the full changelog from previous versions, and include links
to lore for the previous versions.

BTW, it seems like due to a volume of patches and the speed you're
re-sending them over and over, email providers started to reject your
submissions again due to spam detection.  For example, while I'm on
CC list for this patch set, it didn't reach my inbox so far.  So, once
again, please, try not to have too many patches on the list at the same
time and try to avoid re-spinning them too often.

Best regards, Ilya Maximets.