[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFr9PXngrVvcQ2yO0JUj6ve1T39rWftwECnKfUcV3PcKUCPPmg@mail.gmail.com>
Date: Thu, 27 Nov 2025 19:13:17 +0900
From: Daniel Palmer <daniel@...ngy.jp>
To: kernel test robot <lkp@...el.com>
Cc: geert@...ux-m68k.org, oe-kbuild-all@...ts.linux.dev, kas@...nel.org,
mingo@...nel.org, seanjc@...gle.com, bp@...en8.de,
linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] m68k: implement runtime consts
Hi test robot,
On Thu, 27 Nov 2025 at 10:59, kernel test robot <lkp@...el.com> wrote:
> All warnings (new ones prefixed by >>):
>
> In file included from fs/dcache.c:38:
> arch/m68k/include/asm/runtime-const.h: In function '__runtime_fixup_ptr':
> >> arch/m68k/include/asm/runtime-const.h:28:29: warning: unused variable 'end' [-Wunused-variable]
> 28 | const unsigned long end = start + sizeof(*value);
> | ^~~
> arch/m68k/include/asm/runtime-const.h: In function '__runtime_fixup_shift':
> arch/m68k/include/asm/runtime-const.h:51:29: warning: unused variable 'end' [-Wunused-variable]
> 51 | const unsigned long end = start + sizeof(*insn);
> | ^~~
I guess this is because allnoconfig results in CONFIG_MMU=n and that means
that the nommu defines for cache operations are used and those look like:
#define flush_icache_range(start, len) __flush_icache_all()
And the arguments getting passed aren't used. Also noticed that it's
start and len
there not start and end like everywhere else seems to be...
I guess the flush_icache_range macro needs to be tweaked to not
trigger the unused
warning but I'm not sure how right now.
Cheers,
Daniel
Powered by blists - more mailing lists