From: Alison Schofield <alison.schofield@intel.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
<nvdimm@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Dave Jiang" <dave.jiang@intel.com>
Subject: Re: [PATCH v1 1/1] libnvdimm/labels: Get rid of redundant 'else'
Date: Sun, 9 Nov 2025 14:11:54 -0800 [thread overview]
Message-ID: <aRERqoS2aetTyDvL@aschofie-mobl2.lan> (raw)
In-Reply-To: <690e1d0428207_301e35100f6@iweiny-mobl.notmuch>
On Fri, Nov 07, 2025 at 10:23:32AM -0600, Ira Weiny wrote:
>
> Yea putting this in the commit message but more importantly knowing you
> looked through the logic of how claim class is used is what I'm looking
> for.
>
> Thanks,
> Ira
>
Hi Ira,
Coming back around to this patch after a few days, after initially
commenting on the unexplained behavior change, I realize a better
response would have been a simple NAK.
This patch demonstrates why style-only cleanups are generally discouraged
outside of drivers/staging. It creates code churn without fixing bugs
or adding functionality, the changes aren't justified in the commit
message, it adds risk, and consumes limited reviewer and maintainer
bandwidth.
To recoup value from the time already spent on this, I suggest using
this opportunity to set a clear position and precedent, like:
"Style cleanups are not welcomed in the NVDIMM subsystem unless
they're part of a fix or a patch series that includes substantive
changes to the same code area."
FWIW, if folks are looking to dive into this code, there is a patchset
in review here[1] that adds new functionality to this area. Reviews,
including style reviews, are welcomed.
Regardless of a commit message update or a change to the code, this
one is a NAK from me.
--Alison
[1] https://lore.kernel.org/nvdimm/20250917132940.1566437-1-s.neeraj@samsung.com/
next prev parent reply other threads:[~2025-11-09 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 18:37 [PATCH v1 1/1] libnvdimm/labels: Get rid of redundant 'else' Andy Shevchenko
2025-11-05 19:18 ` Ira Weiny
2025-11-06 7:37 ` Andy Shevchenko
2025-11-06 20:57 ` Alison Schofield
2025-11-07 0:46 ` Ira Weiny
2025-11-07 7:39 ` Andy Shevchenko
2025-11-07 16:23 ` Ira Weiny
2025-11-09 22:11 ` Alison Schofield [this message]
2025-11-10 8:50 ` Andy Shevchenko
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=aRERqoS2aetTyDvL@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@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