Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Hildenbrand <david@redhat.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	kasan-dev <kasan-dev@googlegroups.com>,
	linux-mm <linux-mm@kvack.org>,
	open list <linux-kernel@vger.kernel.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	linux-s390@vger.kernel.org, lkft-triage@lists.linaro.org,
	Linux Regressions <regressions@lists.linux.dev>,
	Andrew Morton <akpm@linuxfoundation.org>,
	Kevin Brodsky <kevin.brodsky@arm.com>,
	Andrey Ryabinin <ryabinin.a.a@gmail.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>,
	Ben Copeland <benjamin.copeland@linaro.org>
Subject: Re: next-20250912: riscv: s390: mm/kasan/shadow.c 'kasan_populate_vmalloc_pte' pgtable.h:247:41: error: statement with no effect [-Werror=unused-value]
Date: Fri, 12 Sep 2025 16:12:40 -0700	[thread overview]
Message-ID: <20250912161240.0a5fac78fed5ed8ddc32450a@linux-foundation.org> (raw)
In-Reply-To: <d7a03a2b-d950-4645-80f2-63830bd84f76@redhat.com>

On Fri, 12 Sep 2025 13:34:37 +0200 David Hildenbrand <david@redhat.com> wrote:

> > [-Werror=unused-value]
> >    247 | #define arch_enter_lazy_mmu_mode()      (LAZY_MMU_DEFAULT)
> >        |                                         ^
> > mm/kasan/shadow.c:322:9: note: in expansion of macro 'arch_enter_lazy_mmu_mode'
> >    322 |         arch_enter_lazy_mmu_mode();
> >        |         ^~~~~~~~~~~~~~~~~~~~~~~~
> > mm/kasan/shadow.c: In function 'kasan_depopulate_vmalloc_pte':
> > include/linux/pgtable.h:247:41: error: statement with no effect
> > [-Werror=unused-value]
> >    247 | #define arch_enter_lazy_mmu_mode()      (LAZY_MMU_DEFAULT)
> >        |                                         ^
> > mm/kasan/shadow.c:497:9: note: in expansion of macro 'arch_enter_lazy_mmu_mode'
> >    497 |         arch_enter_lazy_mmu_mode();
> >        |         ^~~~~~~~~~~~~~~~~~~~~~~~
> > cc1: all warnings being treated as errors
> > 
> 
> 
> I'm afraid these changes landed in -mm-unstable a bit too early.
> 

OK, I'll drop Patch series "Nesting support for lazy MMU mode", v2.


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2025-09-12 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 11:32 next-20250912: riscv: s390: mm/kasan/shadow.c 'kasan_populate_vmalloc_pte' pgtable.h:247:41: error: statement with no effect [-Werror=unused-value] Naresh Kamboju
2025-09-12 11:34 ` David Hildenbrand
2025-09-12 23:12   ` 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=20250912161240.0a5fac78fed5ed8ddc32450a@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=akpm@linuxfoundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=benjamin.copeland@linaro.org \
    --cc=dan.carpenter@linaro.org \
    --cc=david@redhat.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=kevin.brodsky@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    --cc=ryabinin.a.a@gmail.com \
    /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