diff mbox series

[net,v2] docs: netdev: document guidance on cleanup patches

Message ID 20241009-doc-mc-clean-v2-1-e637b665fa81@kernel.org (mailing list archive)
State Accepted
Commit aeb218d900e3ea2cc3878ba92cb4758227075358
Delegated to: Netdev Maintainers
Headers show
Series [net,v2] docs: netdev: document guidance on cleanup patches | expand

Checks

Context Check Description
netdev/series_format success Single patches do not need cover letters
netdev/tree_selection success Clearly marked for net
netdev/ynl success Generated files up to date; no warnings/errors; no diff in generated;
netdev/fixes_present success No Fixes tags, but series doesn't touch code
netdev/header_inline success No static functions without inline keyword in header files
netdev/build_32bit success Errors and warnings before: 5 this patch: 5
netdev/build_tools success No tools touched, skip
netdev/cc_maintainers success CCed 7 of 7 maintainers
netdev/build_clang success Errors and warnings before: 5 this patch: 5
netdev/verify_signedoff fail author Signed-off-by missing
netdev/deprecated_api success None detected
netdev/check_selftest success No net selftest shell script
netdev/verify_fixes success No Fixes tag
netdev/build_allmodconfig_warn success Errors and warnings before: 3 this patch: 3
netdev/checkpatch success total: 0 errors, 0 warnings, 0 checks, 29 lines checked
netdev/build_clang_rust success No Rust files in patch. Skipping build
netdev/kdoc success Errors and warnings before: 0 this patch: 0
netdev/source_inline success Was 0 now: 0
netdev/contest success net-next-2024-10-10--09-00 (tests: 775)

Commit Message

Simon Horman Oct. 9, 2024, 9:12 a.m. UTC
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>
---
Changes in v2:
- Drop RFC designation
- Correct capitalisation of heading
- Add that:
  + devm_ conversions are also discouraged, outside the context of other work
  + 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(+)

Comments

Przemek Kitszel Oct. 9, 2024, 9:42 a.m. UTC | #1
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
>   ~~~~~~~~~~~~~~~~~~~~~~
Simon Horman Oct. 9, 2024, 12:50 p.m. UTC | #2
On Wed, Oct 09, 2024 at 11:42:14AM +0200, Przemek Kitszel wrote:
> 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

I agree that there is room to expand on that.  But I would rather defer on
that, because, as mentioned by Jakub in his review of v1, that quickly
becomes quite subjective.

IOW, let's start with something and improve on it later.

...
patchwork-bot+netdevbpf@kernel.org Oct. 10, 2024, 4:10 p.m. UTC | #3
Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 09 Oct 2024 10:12:19 +0100 you 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.
> 
> [...]

Here is the summary with links:
  - [net,v2] docs: netdev: document guidance on cleanup patches
    https://git.kernel.org/netdev/net/c/aeb218d900e3

You are awesome, thank you!
diff mbox series

Patch

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
 ~~~~~~~~~~~~~~~~~~~~~~