From: Reinette Chatre <reinette.chatre@intel.com>
To: Dave Martin <Dave.Martin@arm.com>,
Erick Karanja <karanja99erick@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<tony.luck@intel.com>, <julia.lawall@inria.fr>,
<james.morse@arm.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs/resctrl: Convert lock to guard
Date: Wed, 3 Sep 2025 10:34:05 -0700 [thread overview]
Message-ID: <e250561d-8553-46c1-a285-ddad10a15ee6@intel.com> (raw)
In-Reply-To: <aLhSlXbj+GNQzpJU@e133380.arm.com>
On 9/3/25 7:37 AM, Dave Martin wrote:
> Hi,
>
> You seem already to have been told that patches of this sort are
> unlikely to be helpful. Greg summed it up pretty well, e.g. [1], [2].
>
>
> With regard to this specific patch:
>
> On Wed, Sep 03, 2025 at 03:20:15PM +0300, Erick Karanja wrote:
>> Convert manual lock/unlock calls to guard and tidy up the code.
>
> The very first sentence under "Describe your changes"
> in submitting-patches.rst is: "Describe your problem."
>
> So, what problem is being addressed by this patch?
>
>> Generated-by: Coccinelle SmPL
>> Signed-off-by: Erick Karanja <karanja99erick@gmail.com>
>
> Coccinelle is a powerful tool, but ultimately somebody has to take
> responsibility for the correctness of the output. How have you
> verified that the result is correct?
>
> Also, this is a lot of diffstat for what is really just a change of
> coding style that fixes nothing (or at least, you don't claim that it
> fixes anything).
>
> While all contributions are welcome, they do need to deliver a net
> benefit.
Well said. Thanks Dave.
>
> I can't speak for the maintainers, but given the pain that they would
> likely have fixing up all the merge conflicts that this patch would
> cause, I think that the benefit would need to be substantial.
There just happened to be a similar change suggested for SGX that provides
insight into x86 maintainers' view that I fully agree with:
https://lore.kernel.org/lkml/d9a76e90-7723-49ee-b3ec-85c7533d8023@intel.com/
>
>
> If you found actual bugs as part of this process, then that would
> definitely be worth looking at (?)
ack.
Reinette
prev parent reply other threads:[~2025-09-03 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 12:20 Erick Karanja
2025-09-03 12:41 ` Ilpo Järvinen
2025-09-03 14:37 ` Dave Martin
2025-09-03 17:34 ` Reinette Chatre [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=e250561d-8553-46c1-a285-ddad10a15ee6@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=julia.lawall@inria.fr \
--cc=karanja99erick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®