From: Jakub Kicinski <kuba@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Bart Van Assche <bvanassche@acm.org>,
linux-mm@kvack.org, Ivan Shapovalov <intelfx@intelfx.name>,
Vlastimil Babka <vbabka@suse.cz>,
David Laight <david.laight@aculab.com>,
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>,
llvm@lists.linux.dev
Subject: Re: [PATCH] mm: Fix clang W=1 compiler warnings
Date: Mon, 10 Feb 2025 10:33:03 -0800 [thread overview]
Message-ID: <20250210103303.6ab646d0@kernel.org> (raw)
In-Reply-To: <CAHk-=wiSuP=s4vzdT3TLjDfcj4XJDDvOO1bDj2Zd2EJNc6o=KQ@mail.gmail.com>
On Fri, 7 Feb 2025 20:24:18 -0800 Linus Torvalds wrote:
> > I will take your patch to move it to W=2.
>
> Ok, applied and pushed out as commit 8f6629c004b1 ("kbuild: Move
> -Wenum-enum-conversion to W=2").
>
> Jakub, hopefully this fixes your situation,
Much appreciated, thank you!
next prev parent reply other threads:[~2025-02-10 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 19:12 [PATCH] mm: Fix clang W=1 compiler warnings 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 [this message]
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
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=20250210103303.6ab646d0@kernel.org \
--to=kuba@kernel.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=llvm@lists.linux.dev \
--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 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.