From: patchwork-bot+netdevbpf@kernel.org
To: Donald Hunter <donald.hunter@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, matttbe@kernel.org,
gal@nvidia.com, jstancek@redhat.com, liuhangbin@gmail.com,
noren@nvidia.com, netdev@vger.kernel.org, corbet@lwn.net,
ast@fiberby.net, mchehab+huawei@kernel.org,
jacob.e.keller@intel.com, rubenru09@aol.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/13] tools: ynl: clean up pylint issues
Date: Fri, 09 Jan 2026 17:00:24 +0000 [thread overview]
Message-ID: <176797802404.330174.4360642003047959122.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260108161339.29166-1-donald.hunter@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 Jan 2026 16:13:26 +0000 you wrote:
> pylint tools/net/ynl/pyynl reports >850 issues, with a rating of
> 8.59/10. It's hard to spot new issues or genuine code smells in all that
> noise.
>
> Fix the easily fixable issues and suppress the noisy warnings.
>
> pylint tools/net/ynl/pyynl
> ************* Module pyynl.ethtool
> tools/net/ynl/pyynl/ethtool.py:159:5: W0511: TODO: --show-tunnels tunnel-info-get (fixme)
> tools/net/ynl/pyynl/ethtool.py:160:5: W0511: TODO: --show-module module-get (fixme)
> tools/net/ynl/pyynl/ethtool.py:161:5: W0511: TODO: --get-plca-cfg plca-get (fixme)
> tools/net/ynl/pyynl/ethtool.py:162:5: W0511: TODO: --get-plca-status plca-get-status (fixme)
> tools/net/ynl/pyynl/ethtool.py:163:5: W0511: TODO: --show-mm mm-get (fixme)
> tools/net/ynl/pyynl/ethtool.py:164:5: W0511: TODO: --show-fec fec-get (fixme)
> tools/net/ynl/pyynl/ethtool.py:165:5: W0511: TODO: --dump-module-eerpom module-eeprom-get (fixme)
> tools/net/ynl/pyynl/ethtool.py:166:5: W0511: TODO: pse-get (fixme)
> tools/net/ynl/pyynl/ethtool.py:167:5: W0511: TODO: rss-get (fixme)
> tools/net/ynl/pyynl/ethtool.py:179:9: W0511: TODO: parse the bitmask (fixme)
> tools/net/ynl/pyynl/ethtool.py:196:9: W0511: TODO: parse the bitmask (fixme)
> tools/net/ynl/pyynl/ethtool.py:321:9: W0511: TODO: pass id? (fixme)
> tools/net/ynl/pyynl/ethtool.py:330:17: W0511: TODO: support passing the bitmask (fixme)
> tools/net/ynl/pyynl/ethtool.py:459:5: W0511: TODO: wol-get (fixme)
>
> [...]
Here is the summary with links:
- [net-next,v2,01/13] tools: ynl: pylint suppressions and docstrings
https://git.kernel.org/netdev/net-next/c/37488ae6ceff
- [net-next,v2,02/13] tools: ynl: fix pylint redefinition, encoding errors
https://git.kernel.org/netdev/net-next/c/bcdd8ea73f75
- [net-next,v2,03/13] tools: ynl: fix pylint exception warnings
https://git.kernel.org/netdev/net-next/c/b6270a10b0f8
- [net-next,v2,04/13] tools: ynl: fix pylint dict, indentation, long lines, uninitialised
https://git.kernel.org/netdev/net-next/c/04b0b64e86b7
- [net-next,v2,05/13] tools: ynl: fix pylint misc warnings
https://git.kernel.org/netdev/net-next/c/542ba2de32fb
- [net-next,v2,06/13] tools: ynl: fix pylint global variable related warnings
https://git.kernel.org/netdev/net-next/c/00ef9f153ed8
- [net-next,v2,07/13] tools: ynl: fix logic errors reported by pylint
https://git.kernel.org/netdev/net-next/c/9b6b016df4c2
- [net-next,v2,08/13] tools: ynl: ethtool: fix pylint issues
https://git.kernel.org/netdev/net-next/c/301da4cfea5f
- [net-next,v2,09/13] tools: ynl: fix pylint issues in ynl_gen_rst
https://git.kernel.org/netdev/net-next/c/9a130471f854
- [net-next,v2,10/13] tools: ynl-gen-c: suppress unhelpful pylint messages
https://git.kernel.org/netdev/net-next/c/c2fa97c509ec
- [net-next,v2,11/13] tools: ynl-gen-c: fix pylint warnings for returns, unused, redefined
https://git.kernel.org/netdev/net-next/c/93ef84292959
- [net-next,v2,12/13] tools: ynl-gen-c: fix pylint None, type, dict, generators, init
https://git.kernel.org/netdev/net-next/c/a587f592d6c4
- [net-next,v2,13/13] tools: ynl-gen-c: Fix remaining pylint warnings
https://git.kernel.org/netdev/net-next/c/1ecc8ae876c4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-09 17:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 16:13 [PATCH net-next v2 00/13] tools: ynl: clean up pylint issues Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 01/13] tools: ynl: pylint suppressions and docstrings Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 02/13] tools: ynl: fix pylint redefinition, encoding errors Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 03/13] tools: ynl: fix pylint exception warnings Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 04/13] tools: ynl: fix pylint dict, indentation, long lines, uninitialised Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 05/13] tools: ynl: fix pylint misc warnings Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 06/13] tools: ynl: fix pylint global variable related warnings Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 07/13] tools: ynl: fix logic errors reported by pylint Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 08/13] tools: ynl: ethtool: fix pylint issues Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 09/13] tools: ynl: fix pylint issues in ynl_gen_rst Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 10/13] tools: ynl-gen-c: suppress unhelpful pylint messages Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 11/13] tools: ynl-gen-c: fix pylint warnings for returns, unused, redefined Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 12/13] tools: ynl-gen-c: fix pylint None, type, dict, generators, init Donald Hunter
2026-01-08 16:13 ` [PATCH net-next v2 13/13] tools: ynl-gen-c: Fix remaining pylint warnings Donald Hunter
2026-01-09 17:00 ` patchwork-bot+netdevbpf [this message]
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=176797802404.330174.4360642003047959122.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@fiberby.net \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=matttbe@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=rubenru09@aol.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