From: Hugh Dickins <hughd@google.com>
To: Omkar Wagle <ov.wagle@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
hughd@google.com, akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MM: shmem: Remove code sytle warnings
Date: Wed, 8 Nov 2023 23:46:25 -0800 (PST) [thread overview]
Message-ID: <134bb70e-db8a-0892-0a3c-d00ad57fcece@google.com> (raw)
In-Reply-To: <20231109062228.10227-1-ov.wagle@gmail.com>
mm not MM, style not sytle.
On Wed, 8 Nov 2023, Omkar Wagle wrote:
> Remove most of the code style warnings
>
> Signed-off-by: Omkar Wagle<ov.wagle@gmail.com>
> ---
> mm/shmem.c | 51 +++++++++++++++++++++++++++++++++------------------
> 1 file changed, 33 insertions(+), 18 deletions(-)
Thanks for trying, but I'm sorry: very little of this is an improvement.
Almost all of it is just adding a blank line in between declaration and
code in some small block (including at least one from Linus himself).
checkpatch does a good job of encouraging tidy patches, but it makes no
claim to being right; and that particular nag annoys me more often than
any other (though I often grudgingly give in to it, just for a quiet life
- Cc'ing Matthew because I suspect he resents it even more than I do).
And look at those fsparams: Al and others have gone to the trouble of
lining them up nicely, but you've decided to undo their work.
I believe it's explained somewhere (but admit that a quick look in
Documentation didn't show me where), that checkpatch is something to run
to tidy up your patches, or new source files (or perhaps even staging);
but please don't send its advice on well-established source files.
Hugh
next prev parent reply other threads:[~2023-11-09 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 6:22 [PATCH] MM: shmem: Remove code sytle warnings Omkar Wagle
2023-11-09 7:46 ` Hugh Dickins [this message]
2023-11-09 13:26 ` kernel test robot
2023-11-09 18:49 ` kernel test robot
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=134bb70e-db8a-0892-0a3c-d00ad57fcece@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ov.wagle@gmail.com \
--cc=willy@infradead.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).