From: Linus Torvalds <torvalds@linux-foundation.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Jessica Yu <jeyu@kernel.org>,
Nicolas Pitre <nico@fluxnic.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] kbuild: remove guarding from TRIM_UNUSED_KSYMS
Date: Tue, 9 Mar 2021 11:54:51 -0800 [thread overview]
Message-ID: <CAHk-=wh8qKZYoN-M5a5-=ps7Cf_obtd0P_-0h+nMQEWkVqGFzg@mail.gmail.com> (raw)
In-Reply-To: <20210309151737.345722-5-masahiroy@kernel.org>
On Tue, Mar 9, 2021 at 7:18 AM Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> Now that the build time cost of this option is unnoticeable level,
> revert the following two:
It might still be a good idea to make it depend on EXPERT. Otherwise
you'll have problems with external modules..
Also, can you actually specify that "unnoticeable level" with numbers?
Linus
next prev parent reply other threads:[~2021-03-09 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 15:17 [PATCH v2 0/4] kbuild: build speed improvement of CONFIG_TRIM_UNUSED_KSYMS Masahiro Yamada
2021-03-09 15:17 ` [PATCH v2 1/4] export.h: make __ksymtab_strings per-symbol section Masahiro Yamada
2021-03-09 15:17 ` [PATCH v2 2/4] kbuild: separate out vmlinux.lds generation Masahiro Yamada
2021-03-09 15:17 ` [PATCH v2 3/4] kbuild: re-implement CONFIG_TRIM_UNUSED_KSYMS to make it work in one-pass Masahiro Yamada
2021-03-09 17:36 ` Nicolas Pitre
2021-03-09 18:11 ` Masahiro Yamada
2021-03-09 19:54 ` Nicolas Pitre
2021-03-09 20:11 ` Rasmus Villemoes
2021-03-09 20:45 ` Nicolas Pitre
2021-03-17 15:48 ` kernel test robot
2021-03-09 15:17 ` [PATCH v2 4/4] kbuild: remove guarding from TRIM_UNUSED_KSYMS Masahiro Yamada
2021-03-09 19:54 ` Linus Torvalds [this message]
2021-03-10 12:55 ` kernel test robot
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='CAHk-=wh8qKZYoN-M5a5-=ps7Cf_obtd0P_-0h+nMQEWkVqGFzg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=hch@lst.de \
--cc=jeyu@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nico@fluxnic.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).