From: David Sterba <dsterba@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Sterba <dsterba@suse.com>,
linux-kernel@vger.kernel.org, vbabka@suse.cz
Subject: Re: [GIT PULL] AFFS update for 6.9
Date: Tue, 12 Mar 2024 22:22:59 +0100 [thread overview]
Message-ID: <20240312212259.GX2604@suse.cz> (raw)
In-Reply-To: <CAHk-=wji0u+OOtmAOD-5JV3SXcRJF___k_+8XNKmak0yd5vW1Q@mail.gmail.com>
On Tue, Mar 12, 2024 at 01:02:47PM -0700, Linus Torvalds wrote:
> On Mon, 11 Mar 2024 at 12:37, David Sterba <dsterba@suse.com> wrote:
> >
> > please pull one change to AFFS that removes use of SLAB_MEM_SPREAD,
> > which is going to be removed from MM code.
>
> I've pulled this, but I don't really see the point in removing these
> one by one like this.
>
> SLAB_MEM_SPREAD is already a no-op, the MM people could just do a
> coccinelle thing to remove it everywhere.
That's of course valid and was also suggested as an option. However I
would prefer to let actively maintained code pick the patches first
and then do the rest as sed or coccinelle script. This usually leaves
whitespace damage behind and not everybody takes the care to fix it
manually.
I agree that for AFFS it's a bit too much for just one change but I did
not realize that as I happened to do the same change for btrfs.
> I think you could do 90% even just using a few variations of 'sed', eg
> variations on
>
> git grep -l 'SLAB_MEM_SPREAD' |
> xargs sed -i 's/SLAB_MEM_SPREAD *|//'
>
> git grep -l 'SLAB_MEM_SPREAD' |
> xargs sed -i 's/| *SLAB_MEM_SPREAD//'
>
> and then some manual fixups for (a) whitespace cleanup of the result
> and (b) the couple of cases where it wasn't a bitwise or into other
> fields (or where the bitwise or was on a different line)
>
> And then you'd end up with something like the attached.
I don't know if MM people have such change queued but you could apply
the diff at the end of 6.9, the formatting seems OK.
next prev parent reply other threads:[~2024-03-12 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 19:30 [GIT PULL] AFFS update for 6.9 David Sterba
2024-03-12 20:02 ` Linus Torvalds
2024-03-12 21:22 ` David Sterba [this message]
2024-03-12 22:24 ` pr-tracker-bot
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=20240312212259.GX2604@suse.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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