[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ymt3LnsB7zt+1l2X@atomide.com>
Date: Fri, 29 Apr 2022 08:27:10 +0300
From: Tony Lindgren <tony@...mide.com>
To: Arnd Bergmann <arnd@...nel.org>
Cc: linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
jmkrzyszt@...il.com, aaro.koskinen@....fi, vireshk@...nel.org,
shiraz.linux.kernel@...il.com, nsekhar@...com, brgl@...ev.pl,
linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
kernel test robot <lkp@...el.com>
Subject: Re: [PATCH 4/6] ARM: omap: fix address space warnings from sparse
* Arnd Bergmann <arnd@...nel.org> [220428 13:32]:
> mach-omap2/sram.c:78:17: warning: cast removes address space '__iomem' of expression
> mach-omap2/omap4-common.c:142:27: warning: incorrect type in assignment (different address spaces)
> mach-omap2/omap4-common.c:142:27: expected void [noderef] __iomem *static [toplevel] sram_sync
> mach-omap2/omap4-common.c:142:27: got void *
> mach-omap2/pm34xx.c:113:45: warning: incorrect type in argument 1 (different address spaces)
> mach-omap2/pm34xx.c:113:45: expected void [noderef] __iomem *save_regs
> mach-omap2/pm34xx.c:113:45: got void *extern [addressable] [toplevel] omap3_secure_ram_storage
These omap2 specific warnings seem to have been split out into a separate
patch, or maybe a patch hunk is missing here?
> arch/arm/mach-omap1/board-ams-delta.c | 2 +-
> arch/arm/mach-omap1/sram-init.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
As this touches only omap1 files. If this patch will be omap1 specific,
maybe update the subject line too?
Regards,
Tony
Powered by blists - more mailing lists