From: Nicholas Piggin <npiggin@gmail.com>
To: linux-kbuild@vger.kernel.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>
Subject: [PATCH 0/2] remove the last of incremental linking
Date: Sun, 11 Feb 2018 00:25:02 +1000 [thread overview]
Message-ID: <20180210142504.29890-1-npiggin@gmail.com> (raw)
I don't think there is any point to keeping around the deprecated
incremental linking option for too long. So I propose to remove it.
After that is removed, I wonder what people think of changing from
built-in.o to built-in.a?
Thanks,
Nick
Nicholas Piggin (2):
kbuild: remove incremental linking option
kbuild: rename built-in.o to built-in.a
Documentation/kbuild/makefiles.txt | 22 ++++++---
Documentation/process/changes.rst | 2 +-
Makefile | 14 +++---
arch/Kconfig | 6 ---
arch/blackfin/kernel/bfin_ksyms.c | 2 +-
arch/powerpc/kernel/Makefile | 2 +-
drivers/s390/Makefile | 2 +-
lib/Kconfig.debug | 4 +-
scripts/Makefile.build | 38 ++++++---------
scripts/Makefile.lib | 6 +--
scripts/link-vmlinux.sh | 99 ++++++++++++++------------------------
scripts/namespace.pl | 2 +-
usr/initramfs_data.S | 2 +-
13 files changed, 82 insertions(+), 119 deletions(-)
--
2.15.1
next reply other threads:[~2018-02-10 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 14:25 Nicholas Piggin [this message]
2018-02-10 14:25 ` [PATCH 1/2] kbuild: remove incremental linking option Nicholas Piggin
2018-02-11 6:04 ` Masahiro Yamada
2018-02-18 14:26 ` Sam Ravnborg
2018-02-18 16:53 ` Nicholas Piggin
2018-02-10 14:25 ` [PATCH 2/2] kbuild: rename built-in.o to built-in.a Nicholas Piggin
2018-02-11 4:38 ` Masahiro Yamada
2018-02-11 11:15 ` Nicholas Piggin
2018-02-12 0:57 ` Masahiro Yamada
2018-02-12 1:26 ` Nicolas Pitre
2018-02-12 3:00 ` Masahiro Yamada
2018-02-12 3:08 ` Masahiro Yamada
2018-02-18 17:10 ` Sam Ravnborg
2018-02-19 7:04 ` Nicholas Piggin
2018-02-18 23:42 ` [PATCH 0/2] remove the last of incremental linking Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180210142504.29890-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.