public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Nicolas Bretz <bretznic@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] ext4: inode: Delete braces for single statements
Date: Thu, 17 Oct 2024 20:19:53 -0400	[thread overview]
Message-ID: <20241018001953.GB3204734@mit.edu> (raw)
In-Reply-To: <20241014140654.69613-1-bretznic@gmail.com>

On Mon, Oct 14, 2024 at 07:06:54AM -0700, Nicolas Bretz wrote:
> checkpatch.pl warnings - braces are not necessary
> 
> Signed-off-by: Nicolas Bretz <bretznic@gmail.com>

The checkpatch.pl script is meant to check *patches*, and in general,
in the ext4 subsystem (as with many other subststems) patches which
only fix checkpatch.pl file are discouraged, since it can introduce
potential patch conflicts when cherrypicking fixes, or in the course
of other people doing other development.

Granted, dealing with the patch conflicts aren't that hard, but the
cost/benefit ratio isn't worth it.  For kernel newbies who are looking
for practice submitting patches, cleaning up checkpatch warnings in
the staging subsystem are fine, but in general, it's best to not send
cleanup-only patches to other parts of the system.

Of course, if you're modifying that part of the code in question,
that's a perfect time to clean it up while you're at it.

> Removed trailing whitespaces introduced in v1

In the future, please put changes between the v1 and v2 patches after
the three hyphens (by where the summary of how many lines were added
or removed in each file).  That way the description of changes between
earlier versions aren't preserved forever in the git commit
description, since they aren't really useful once they've landed in
the git.

Thanks,

					- Ted

  reply	other threads:[~2024-10-18  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 14:06 [PATCH v2] ext4: inode: Delete braces for single statements Nicolas Bretz
2024-10-18  0:19 ` Theodore Ts'o [this message]
2024-10-18  0:50   ` Nicolas Bretz

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=20241018001953.GB3204734@mit.edu \
    --to=tytso@mit.edu \
    --cc=bretznic@gmail.com \
    --cc=linux-ext4@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