From: Lee Jones <lee.jones@linaro.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Remy Card <card@masi.ibp.fr>,
"David S. Miller" <davem@caip.rutgers.edu>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/1] fs: ext4: namei: trivial: Fix a couple of small whitespace issues
Date: Fri, 23 Jul 2021 08:25:46 +0100 [thread overview]
Message-ID: <YPpu+qe9HyJUskaY@google.com> (raw)
In-Reply-To: <YPnubECqbX47V3TK@mit.edu>
On Thu, 22 Jul 2021, Theodore Ts'o wrote:
> On Thu, Jul 22, 2021 at 12:35:43PM +0100, Lee Jones wrote:
> > On Thu, 20 May 2021, Lee Jones wrote:
> >
> > > Cc: "Theodore Ts'o" <tytso@mit.edu>
> > > Cc: Andreas Dilger <adilger.kernel@dilger.ca>
> > > Cc: Remy Card <card@masi.ibp.fr>
> > > Cc: "David S. Miller" <davem@caip.rutgers.edu>
> > > Cc: linux-ext4@vger.kernel.org
> > > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> > > ---
> > > fs/ext4/namei.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > Any news on this please?
> >
> > Would you like me to submit a [RESEND]?
>
> Please don't send "checkpatch.pl --file" patches for the ext4 file
> system; if you must, please focus on files in the drivers directory,
> where they are more welcome. If developers are making changes to a
> file, fixing some checkpatch.pl whines is fine, but white-sapace only
> changes just obfuscates "git blame" code archology, and so the costs
> far outwieghs the costs. "Fix" is also not the right verb to use.
> For more information please see [1].
>
> [1] https://gist.github.com/17twenty/8154928
>
> If you are looking for subtantive ways of contributing to the ext4
> file system, feel free to look at various syzbot warnings[2] and try
> to figure out what is going on there.
>
> [2] https://syzkaller.appspot.com/upstream
>
> (In some cases, the syzbot complaint has already been fixed, and it's
> just a matter of letting syzbot knoww that it has since been fixed by
> a particular commit. See [3] for more details.)
>
> [3] https://github.com/google/syzkaller/blob/master/docs/syzbot.md
This patch doesn't have anything to do with checkpatch.
Daniel, who was making more 'substantive' changes to ext4, fixed these
whitespace issues in his first submission [0], but were dropped from
the second revision for some reason and thus didn't make it into
Mainline [1].
This is an attempt to realign his development repo (Android) with
Mainline. I had the choice of either backporting the issues back into
the Android kernel or upstreaming the original whitespace cleanup.
It made more sense to me to draft a patch making one codebase better
than another one worse.
[0] https://lore.kernel.org/linux-fsdevel/20210203090745.4103054-2-drosen@google.com/
[1] 471fbbea7ff70 ext4: handle casefolding with encryption
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2021-07-23 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 12:55 [PATCH 1/1] fs: ext4: namei: trivial: Fix a couple of small whitespace issues Lee Jones
2021-05-27 3:11 ` riteshh
2021-05-27 8:23 ` Lee Jones
2021-07-22 11:35 ` Lee Jones
2021-07-22 22:17 ` Theodore Ts'o
2021-07-23 7:25 ` Lee Jones [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=YPpu+qe9HyJUskaY@google.com \
--to=lee.jones@linaro.org \
--cc=adilger.kernel@dilger.ca \
--cc=card@masi.ibp.fr \
--cc=davem@caip.rutgers.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.