From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: mm-commits@vger.kernel.org, peterx@redhat.com,
joshua.hahnjy@gmail.com, jhubbard@nvidia.com, jgg@ziepe.ca,
dywoq.contact@gmail.com, david@kernel.org, aleks.koyf@gmail.com
Subject: Re: + mm-initialize-seq-in-gup_fast-to-remove-wmaybe-uninitialized-warning.patch added to mm-new branch
Date: Mon, 2 Mar 2026 16:14:12 -0800 [thread overview]
Message-ID: <20260302161412.f5e5c1944509449fb8b11ef9@linux-foundation.org> (raw)
In-Reply-To: <aaYl99AXj-mKHDbO@casper.infradead.org>
On Tue, 3 Mar 2026 00:06:15 +0000 Matthew Wilcox <willy@infradead.org> wrote:
> On Mon, Mar 02, 2026 at 12:43:09PM -0800, Andrew Morton wrote:
> > The patch titled
> > Subject: mm: initialize 'seq' in gup_fast to remove -Wmaybe-uninitialized warning
> > has been added to the -mm mm-new branch. Its filename is
> > mm-initialize-seq-in-gup_fast-to-remove-wmaybe-uninitialized-warning.patch
>
> This was a W=2 warning. We don't usually fix those.
yeah.
I thought there was a more recognized way of enabling this, but it
seems I dreamed it.
otoh, there's value in having people privately testing W=2 - they might
find bugs, so making life better for those people also has value. It
depends how much other noise the W=2 build creates.
<tries it>
./arch/x86/include/asm/text-patching.h: In function '__emulate_cc':
./arch/x86/include/asm/text-patching.h:183:36: error: declaration of 'cc_mask' s
immediate fail. How are people even using this thing?
prev parent reply other threads:[~2026-03-03 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 20:43 + mm-initialize-seq-in-gup_fast-to-remove-wmaybe-uninitialized-warning.patch added to mm-new branch Andrew Morton
2026-03-02 21:08 ` David Hildenbrand (Arm)
2026-03-02 22:09 ` Andrew Morton
2026-03-03 0:06 ` Matthew Wilcox
2026-03-03 0:14 ` Andrew Morton [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=20260302161412.f5e5c1944509449fb8b11ef9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aleks.koyf@gmail.com \
--cc=david@kernel.org \
--cc=dywoq.contact@gmail.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=joshua.hahnjy@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=peterx@redhat.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 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.