From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, steved@redhat.com
Cc: anna@kernel.org
Subject: [PATCH nfs-utils v2 0/8] rpcctl: Flake8 cleanups
Date: Wed, 15 Jan 2025 15:20:27 -0500 [thread overview]
Message-ID: <20250115202035.112122-1-anna@kernel.org> (raw)
From: Anna Schumaker <anna.schumaker@oracle.com>
This is a series of cleanups for rpcctl.py to fix up various style
issues after running `flake8` on the code.
Thoughts?
Anna
Anna Schumaker (7):
rpcctl: Fix flake8 whitespace errors
rpcctl: Fix flake8 line-too-long errors
rpcctl: Fix flake8 bare exception error
rpcctl: Fix flake8 ambiguous-variable-name error
rpcctl: Add missing docstrings to the Xprt class
rpcctl: Add missing docstrings to the XprtSwitch class
rpcctl: Add remaining missing docstrings
Joshua Kaldon (1):
Patch for broken libnfsimapd static and regex plugins.
support/nfsidmap/Makefile.am | 6 +-
tools/rpcctl/rpcctl.py | 107 ++++++++++++++++++++++++++---------
2 files changed, 83 insertions(+), 30 deletions(-)
--
2.48.1
next reply other threads:[~2025-01-15 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 20:20 Anna Schumaker [this message]
2025-01-15 20:20 ` [PATCH nfs-utils v2 1/8] Patch for broken libnfsimapd static and regex plugins Anna Schumaker
2025-01-15 20:20 ` [PATCH nfs-utils v2 2/8] rpcctl: Fix flake8 whitespace errors Anna Schumaker
2025-01-15 20:20 ` [PATCH nfs-utils v2 3/8] rpcctl: Fix flake8 line-too-long errors Anna Schumaker
2025-01-15 20:20 ` [PATCH nfs-utils v2 4/8] rpcctl: Fix flake8 bare exception error Anna Schumaker
2025-01-15 20:20 ` [PATCH nfs-utils v2 5/8] rpcctl: Fix flake8 ambiguous-variable-name error Anna Schumaker
2025-01-15 20:20 ` [PATCH nfs-utils v2 6/8] rpcctl: Add missing docstrings to the Xprt class Anna Schumaker
2025-01-15 20:20 ` [PATCH nfs-utils v2 7/8] rpcctl: Add missing docstrings to the XprtSwitch class Anna Schumaker
2025-01-15 20:20 ` [PATCH nfs-utils v2 8/8] rpcctl: Add remaining missing docstrings Anna Schumaker
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=20250115202035.112122-1-anna@kernel.org \
--to=anna@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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