From: Matthew Wilcox <willy@infradead.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Ivan Shapovalov <intelfx@intelfx.name>,
David Laight <david.laight@aculab.com>,
Nathan Chancellor <nathan@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
David Rientjes <rientjes@google.com>,
David Hildenbrand <david@redhat.com>,
Kaiyang Zhao <kaiyang2@cs.cmu.edu>,
Joel Granados <joel.granados@kernel.org>,
Sourav Panda <souravpanda@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] mm: Fix clang W=1 compiler warnings
Date: Tue, 11 Feb 2025 19:25:29 +0000 [thread overview]
Message-ID: <Z6ukKQX-Qf-w8kyo@casper.infradead.org> (raw)
In-Reply-To: <02cd4d8e-9451-4785-9664-0d680d5e82e3@acm.org>
On Tue, Feb 11, 2025 at 10:48:47AM -0800, Bart Van Assche wrote:
> On 2/11/25 6:34 AM, Vlastimil Babka wrote:
> > On 2/8/25 11:28, Matthew Wilcox wrote:
> > > this patch was NAKed last year
> >>
> > > https://lore.kernel.org/all/ZnXC5Xa4R0Mp7FCB@casper.infradead.org/
>
> I wasn't Cc-ed on that email thread so I hadn't seen it yet.
Yes, but email lists have archives for a reason. You can always look to
see if you're the first person to encounter a problem.
> > With the warning now in W=2, want to submit the revert of above, Bart?
>
> OK, I will submit a revert of commit 30c2de0a267c ("mm/vmstat: fix a W=1
> clang compiler warning"). I see that Nathan's change already made it in
> Linus' tree as commit 8f6629c004b1 ("kbuild: Move -Wenum-enum-conversion
> to W=2").
Thank you.
prev parent reply other threads:[~2025-02-11 19:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 19:12 Bart Van Assche
2025-02-03 13:32 ` Vlastimil Babka
2025-02-08 0:49 ` Jakub Kicinski
2025-02-08 1:01 ` Linus Torvalds
2025-02-08 1:38 ` Jakub Kicinski
2025-02-08 2:18 ` Nathan Chancellor
2025-02-08 3:11 ` Linus Torvalds
2025-02-08 3:33 ` Nathan Chancellor
2025-02-08 3:49 ` Linus Torvalds
2025-02-08 4:24 ` Linus Torvalds
2025-02-10 18:33 ` Jakub Kicinski
2025-02-08 2:55 ` Bart Van Assche
2025-02-08 3:22 ` Linus Torvalds
2025-02-08 3:30 ` Bart Van Assche
2025-02-08 10:28 ` Matthew Wilcox
2025-02-11 14:34 ` Vlastimil Babka
2025-02-11 18:48 ` Bart Van Assche
2025-02-11 19:25 ` Matthew Wilcox [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=Z6ukKQX-Qf-w8kyo@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=david.laight@aculab.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=intelfx@intelfx.name \
--cc=joel.granados@kernel.org \
--cc=kaiyang2@cs.cmu.edu \
--cc=linux-mm@kvack.org \
--cc=nathan@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=rientjes@google.com \
--cc=souravpanda@google.com \
--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