From: Simon Horman <horms@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: "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>,
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 13:50:21 +0100 [thread overview]
Message-ID: <20241009125021.GU99782@kernel.org> (raw)
In-Reply-To: <01c97823-d560-4f89-b757-752e18940f31@intel.com>
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.
...
next prev parent reply other threads:[~2024-10-09 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 9:12 [PATCH net v2] docs: netdev: document guidance on cleanup patches Simon Horman
2024-10-09 9:42 ` Przemek Kitszel
2024-10-09 12:50 ` Simon Horman [this message]
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=20241009125021.GU99782@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).