From: Christoph Hellwig <hch@infradead.org>
To: Elliot Berman <eberman@codeaurora.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Sami Tolvanen <samitolvanen@google.com>,
Trilok Soni <tsoni@codeaurora.org>,
Mahesh Kumar Kalikot Veetil <mkalikot@codeaurora.org>,
Jeff Johnson <jjohnson@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [RFC 0/2] Kbuild: Support nested composite objects
Date: Wed, 27 Jan 2021 15:51:02 +0000 [thread overview]
Message-ID: <20210127155102.GA1709780@infradead.org> (raw)
In-Reply-To: <1611343638-28206-1-git-send-email-eberman@codeaurora.org>
On Fri, Jan 22, 2021 at 11:27:16AM -0800, Elliot Berman wrote:
> This series was developed after discussion in https://lkml.org/lkml/2021/1/19/850
>
> The motivation for this series is an out-of-tree module which contains a large
> number of source files. This causes Kbuild to exceed the maximum command line
> argument length when linking the files. Proposal here permits composite objects
Please don't even try to bloat the kernel build system for this.
Thanks!
next prev parent reply other threads:[~2021-01-27 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 19:27 [RFC 0/2] Kbuild: Support nested composite objects Elliot Berman
2021-01-22 19:27 ` [RFC 1/2] Kbuild: Make composite object searching more generic Elliot Berman
2021-01-26 18:02 ` Masahiro Yamada
2021-01-22 19:27 ` [RFC 2/2] Kbuild: Support nested composite objects Elliot Berman
2021-01-26 17:59 ` [RFC 0/2] " Masahiro Yamada
2021-01-27 15:51 ` Christoph Hellwig [this message]
2021-06-13 16:19 ` Trent Piepho
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=20210127155102.GA1709780@infradead.org \
--to=hch@infradead.org \
--cc=eberman@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=jjohnson@codeaurora.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mkalikot@codeaurora.org \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.com \
--cc=tsoni@codeaurora.org \
/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