From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Simon Horman <horms@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: <netdev@vger.kernel.org>, <workflows@vger.kernel.org>,
<linux-doc@vger.kernel.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH net v2] docs: netdev: document guidance on cleanup patches
Date: Wed, 9 Oct 2024 11:42:14 +0200 [thread overview]
Message-ID: <01c97823-d560-4f89-b757-752e18940f31@intel.com> (raw)
In-Reply-To: <20241009-doc-mc-clean-v2-1-e637b665fa81@kernel.org>
On 10/9/24 11:12, Simon Horman wrote:
> The purpose of this section is to document what is the current practice
> regarding clean-up patches which address checkpatch warnings and similar
> problems. I feel there is a value in having this documented so others
> can easily refer to it.
>
> Clearly this topic is subjective. And to some extent the current
> practice discourages a wider range of patches than is described here.
> But I feel it is best to start somewhere, with the most well established
> part of the current practice.
>
> --
> I did think this was already documented. And perhaps it is.
> But I was unable to find it after a quick search.
>
> Signed-off-by: Simon Horman <horms@kernel.org>
Looks like you wanted to say "please don't submit autogenerated clenups"
> ---
> Changes in v2:
> - Drop RFC designation
> - Correct capitalisation of heading
> - Add that:
> + devm_ conversions are also discouraged, outside the context of other work
devm_ is generally discouraged in netdev, so much that I will welcome
the opposite cleanup :)
Your write-up on this is correct, no objections.
Perhaps we could say more about the status of the code that is fixed -
Maintained/Odd fixes/Orphaned - I would don't touch anything below
"Maintained" for good reason
> + Spelling and grammar fixes are not discouraged
> - Reformat text accordingly
> - Link to v1: https://lore.kernel.org/r/20241004-doc-mc-clean-v1-1-20c28dcb0d52@kernel.org
> ---
> Documentation/process/maintainer-netdev.rst | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst
> index c9edf9e7362d..1ae71e31591c 100644
> --- a/Documentation/process/maintainer-netdev.rst
> +++ b/Documentation/process/maintainer-netdev.rst
> @@ -355,6 +355,8 @@ just do it. As a result, a sequence of smaller series gets merged quicker and
> with better review coverage. Re-posting large series also increases the mailing
> list traffic.
>
> +.. _rcs:
> +
> Local variable ordering ("reverse xmas tree", "RCS")
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> @@ -391,6 +393,21 @@ APIs and helpers, especially scoped iterators. However, direct use of
> ``__free()`` within networking core and drivers is discouraged.
> Similar guidance applies to declaring variables mid-function.
>
> +Clean-up patches
> +~~~~~~~~~~~~~~~~
> +
> +Netdev discourages patches which perform simple clean-ups, which are not in
> +the context of other work. For example:
> +
> +* Addressing ``checkpatch.pl`` warnings
> +* Addressing :ref:`Local variable ordering<rcs>` issues
> +* Conversions to device-managed APIs (``devm_`` helpers)
> +
> +This is because it is felt that the churn that such changes produce comes
> +at a greater cost than the value of such clean-ups.
> +
> +Conversely, spelling and grammar fixes are not discouraged.
> +
> Resending after review
> ~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2024-10-09 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 9:12 Simon Horman
2024-10-09 9:42 ` Przemek Kitszel [this message]
2024-10-09 12:50 ` Simon Horman
2024-10-10 16:10 ` patchwork-bot+netdevbpf
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=01c97823-d560-4f89-b757-752e18940f31@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=workflows@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