From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Wed, 6 Dec 2017 07:57:14 -0800 Subject: [PATCH] ARM: omap2: hide omap3_save_secure_ram on non-OMAP3 builds In-Reply-To: <20171206141517.670032-1-arnd@arndb.de> References: <20171206141517.670032-1-arnd@arndb.de> Message-ID: <20171206155714.GY28152@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Arnd Bergmann [171206 14:18]: > In configurations without CONFIG_OMAP3 but with secure RAM support, > we now run into a link failure: > > arch/arm/mach-omap2/omap-secure.o: In function `omap3_save_secure_ram': > omap-secure.c:(.text+0x130): undefined reference to `save_secure_ram_context' > > The omap3_save_secure_ram() function is only called from the OMAP34xx > power management code, so we can simply hide that function in the > appropriate #ifdef. > > Fixes: d09220a887f7 ("ARM: OMAP2+: Fix SRAM virt to phys translation for save_secure_ram_context") > Signed-off-by: Arnd Bergmann Thanks for fixing it, want to apply directly to ARM SoC fixes where d09220a887f7 is now? If so: Acked-by: Tony Lindgren Regards, Tony > --- > arch/arm/mach-omap2/omap-secure.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/arm/mach-omap2/omap-secure.c b/arch/arm/mach-omap2/omap-secure.c > index f9303dc631e4..7be95cd8136d 100644 > --- a/arch/arm/mach-omap2/omap-secure.c > +++ b/arch/arm/mach-omap2/omap-secure.c > @@ -72,6 +72,7 @@ phys_addr_t omap_secure_ram_mempool_base(void) > return omap_secure_memblock_base; > } > > +#ifdef CONFIG_ARCH_OMAP3 > u32 omap3_save_secure_ram(void __iomem *addr, int size) > { > u32 ret; > @@ -90,6 +91,7 @@ u32 omap3_save_secure_ram(void __iomem *addr, int size) > > return ret; > } > +#endif > > /** > * rx51_secure_dispatcher: Routine to dispatch secure PPA API calls > -- > 2.9.0 > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel