From: Minxi Hou <houminxi@gmail.com>
To: netdev@vger.kernel.org
Cc: aconole@redhat.com, echaudron@redhat.com, i.maximets@redhat.com,
dev@openvswitch.org
Subject: Re: [PATCH net-next 0/4] selftests: openvswitch: pylint cleanup of ovs-dpctl.py
Date: Sun, 6 Sep 2026 04:55:40 -0400 [thread overview]
Message-ID: <20260906085540.609993-1-houminxi@gmail.com> (raw)
In-Reply-To: <20260905104026.3776396-1-houminxi@gmail.com>
Hi all,
This series is a respin of the pylint cleanup I posted in May [1],
which got a changes-requested. I forgot to tag it as v2, sorry for
the confusion.
Changes since v1:
- Dropped the patch that renamed the NLA classes to snake_case. Those
names mirror the kernel-side netlink attribute enums, so keeping
them as-is makes the mapping obvious and avoids a large
cosmetic-only diff.
- Rebased onto current net-next (base-commit 9eab111e7657).
- Pylint score is now 9.93/10 (upstream file scores 7.66/10).
On the direction Aaron raised in the v1 thread: moving ovs-dpctl.py
from pyroute2 to the in-tree YNL specs is still the right move, and
the gaps I listed back then (no ovs_packet.yaml or conntrack specs,
datapath flow operations and attributes missing from the family spec)
still stand. This cleanup is complementary to that migration: it
clears the mechanical noise now and shrinks the diff any future YNL
rewrite has to carry. Happy to pick up the migration discussion
separately, offline works for me.
[1] https://lore.kernel.org/netdev/20260513121240.2590767-1-houminxi@gmail.com/
Thanks,
Minxi
next prev parent reply other threads:[~2026-09-06 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 10:40 [PATCH net-next 0/4] selftests: openvswitch: pylint cleanup of ovs-dpctl.py Minxi Hou
2026-09-05 10:40 ` [PATCH 1/4] selftests: openvswitch: convert %-formatting to f-strings Minxi Hou
2026-09-09 12:42 ` netdev-bot+sashiko
2026-09-05 10:40 ` [PATCH 2/4] selftests: openvswitch: fix misc pylint warnings in ovs-dpctl.py Minxi Hou
2026-09-09 12:42 ` netdev-bot+sashiko
2026-09-05 10:40 ` [PATCH 3/4] selftests: openvswitch: add missing docstrings " Minxi Hou
2026-09-09 12:42 ` netdev-bot+sashiko
2026-09-05 10:40 ` [PATCH 4/4] selftests: openvswitch: suppress pylint complexity warnings Minxi Hou
2026-09-09 12:42 ` netdev-bot+sashiko
2026-09-06 8:55 ` Minxi Hou [this message]
2026-09-08 17:04 ` [net-next,0/4] selftests: openvswitch: pylint cleanup of ovs-dpctl.py Minxi Hou
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=20260906085540.609993-1-houminxi@gmail.com \
--to=houminxi@gmail.com \
--cc=aconole@redhat.com \
--cc=dev@openvswitch.org \
--cc=echaudron@redhat.com \
--cc=i.maximets@redhat.com \
--cc=netdev@vger.kernel.org \
/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