From: Masahiro Yamada <masahiroy@kernel.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
Ben Hutchings <ben@decadent.org.uk>,
linux-snps-arc@lists.infradead.org
Subject: Re: [PATCH] kbuild: builddeb: always make modules_install, to install modules.builtin*
Date: Mon, 26 Jun 2023 03:24:33 +0900 [thread overview]
Message-ID: <CAK7LNARLti=Cp1WRAzMufXpXLvM=X1WHLN1RT=-ZAc1q06pPcw@mail.gmail.com> (raw)
In-Reply-To: <f7e9220aad3d98bd174f7dcbd68031e1e15ea968.1687461492.git.josh@joshtriplett.org>
On Fri, Jun 23, 2023 at 4:20 AM Josh Triplett <josh@joshtriplett.org> wrote:
>
> Even for a non-modular kernel, the kernel builds modules.builtin and
> modules.builtin.modinfo, with information about the built-in modules.
> Tools such as initramfs-tools need these files to build a working
> initramfs on some systems, such as those requiring firmware.
>
> Now that `make modules_install` works even in non-modular kernels and
> installs these files, unconditionally invoke it when building a Debian
> package.
>
> Signed-off-by: Josh Triplett <josh@joshtriplett.org>
> ---
Applied to linux-kbuild. Thanks.
What I meant in my previous reply was
to remove "if is_enabled CONFIG_MODULES; then"
Anyway, I did it by myself in a follow-up patch.
https://lore.kernel.org/linux-kbuild/20230625181623.2473308-1-masahiroy@kernel.org/T/#u
--
Best Regards
Masahiro Yamada
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
prev parent reply other threads:[~2023-06-25 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 11:17 [PATCH] kbuild: make modules_install copy modules.builtin(.modinfo) Masahiro Yamada
2023-06-19 12:34 ` Nicolas Schier
2023-06-22 19:11 ` Josh Triplett
2023-06-22 19:19 ` [PATCH] kbuild: builddeb: always make modules_install, to install modules.builtin* Josh Triplett
2023-06-23 20:55 ` Nicolas Schier
2023-06-25 18:24 ` Masahiro Yamada [this message]
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='CAK7LNARLti=Cp1WRAzMufXpXLvM=X1WHLN1RT=-ZAc1q06pPcw@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=ben@decadent.org.uk \
--cc=josh@joshtriplett.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).