From: Andrew Morton <akpm@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
"Ankur Arora" <ankur.a.arora@oracle.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
"Andreas Schwab" <schwab@linux-m68k.org>
Subject: Re: [PATCH v2] m68k: Avoid -Wunused-but-set-parameter in clear_user_page()
Date: Wed, 1 Jul 2026 16:12:14 -0700 [thread overview]
Message-ID: <20260701161214.5f381f2882af5fffd909a0b1@linux-foundation.org> (raw)
In-Reply-To: <CAMuHMdXsfo=BR-e7gBKvTx=cH84vQoNXN8hZv9+8E+EmirMpEQ@mail.gmail.com>
On Wed, 1 Jul 2026 11:48:35 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > --- a/arch/m68k/include/asm/page_mm.h
> > > +++ b/arch/m68k/include/asm/page_mm.h
> > > @@ -55,10 +55,12 @@ static inline void clear_page(void *page)
> > > #define clear_user_page(addr, vaddr, page) \
> > > do { clear_page(addr); \
> > > flush_dcache_page(page); \
> > > + (void)(vaddr); \
> > > } while (0)
> > > #define copy_user_page(to, from, vaddr, page) \
> > > do { copy_page(to, from); \
> > > flush_dcache_page(page); \
> > > + (void)(vaddr); \
> > > } while (0)
> > >
> > > extern unsigned long m68k_memoffset;
>
> People are starting to report this, now gcc-16 is getting more
> widespread use.
>
> Andrew: can you please take this, or shall I queue it for m68k fixes
> (I don't have any other fixes at the moment)?
>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Sorry, this fell through a crack. I've queued it for 7.2-rcX,
cc:stable.
next prev parent reply other threads:[~2026-07-01 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 8:33 Thomas Weißschuh
2026-05-25 19:54 ` Andrew Morton
2026-07-01 9:48 ` Geert Uytterhoeven
2026-07-01 23:12 ` Andrew Morton [this message]
2026-07-02 8:07 ` Geert Uytterhoeven
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=20260701161214.5f381f2882af5fffd909a0b1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ankur.a.arora@oracle.com \
--cc=david@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux@weissschuh.net \
--cc=schwab@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox