linux-kernel - Re: [PATCH 2/2] MIPS: fix duplicated slashes for Platform file path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 9 Nov 2021 16:32:40 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] MIPS: fix duplicated slashes for Platform file path

On Wed, Nov 10, 2021 at 12:01:46AM +0900, Masahiro Yamada wrote:
> platform-y accumulates platform names with a slash appended.
> The current $(patsubst ...) ends up with doubling slashes.
> 
> GNU Make still include Platform files, but in case of an error,
> a clumsy file path is displayed:
> 
>   arch/mips/loongson2ef//Platform:36: *** only binutils >= 2.20.2 have needed option -mfix-loongson2f-nop.  Stop.
> 
> Signed-off-by: Masahiro Yamada <masahiroy@...nel.org>
> ---
> 
>  arch/mips/Kbuild.platforms | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/mips/Kbuild.platforms b/arch/mips/Kbuild.platforms
> index 2c57994b5217..30193bcf9caa 100644
> --- a/arch/mips/Kbuild.platforms
> +++ b/arch/mips/Kbuild.platforms
> @@ -37,4 +37,4 @@ platform-$(CONFIG_MACH_TX49XX)		+= txx9/
>  platform-$(CONFIG_MACH_VR41XX)		+= vr41xx/
>  
>  # include the platform specific files
> -include $(patsubst %, $(srctree)/arch/mips/%/Platform, $(platform-y))
> +include $(patsubst %/, $(srctree)/arch/mips/%/Platform, $(platform-y))
> -- 
> 2.30.2

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]