[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sat, 5 May 2018 19:16:13 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
linux-arch <linux-arch@...r.kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Steven Miao <realmz6@...il.com>,
James Hogan <jhogan@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: [RFC] Removal of CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX
Hi.
CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX was selected
by BLACKFIN and METAG.
Now that both architectures removed in the previous
merge window, there is no more user of this CONFIG option.
My question is,
is it OK to remove CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX entirely?
In other words,
- Is there possibility to revive Blackfin/Metag support?
- Do future architectures need HAVE_UNDERSCORE_SYMBOL_PREFIX?
I guess (hope) they are unlikely to happen.
If we can remove CONFIG_HAVE_UNDERSCORE_SYMBOL_PREFIX,
several tools (modpost, genksyms, adjust_autoksyms.sh, etc.)
will be simplified.
Also, VMLINUX_SYMBOL() in include/asm-generic/vmlinux.lds.h
can be removed. So, the linker script will become more readable.
Is it OK to move forward the clean-ups?
Comments are appreciated.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists