linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Nicolas Schier <nsc@kernel.org>
Cc: Alexey Gladkov <legion@kernel.org>,
	Petr Pavlu <petr.pavlu@suse.com>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	Daniel Gomez <da.gomez@samsung.com>,
	linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
	linux-kbuild@vger.kernel.org,
	Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH v7 3/8] kbuild: keep .modinfo section in vmlinux.unstripped
Date: Tue, 16 Sep 2025 18:10:10 -0700	[thread overview]
Message-ID: <20250917011010.GA3106929@ax162> (raw)
In-Reply-To: <aMll6cHPhIY2yswz@levanger>

On Tue, Sep 16, 2025 at 03:28:09PM +0200, Nicolas Schier wrote:
> yeah, it's actually because I dislike modifying vmlinux.unstripped in
> the vmlinux rule.
> 
> But it may be that Nathan does not see it this way.

Yeah, I would agree that it is good form to avoid modifying the inputs
of a rule.

This warning is pretty annoying since it is intentional but we do not
have great tools to hide just this one instance it seems... This is
probably worth a comment.

It would be nice if this section could be marked as NOLOAD from the
beginning but that will mess with extracting .modinfo via objcopy from
my brief testing.

Cheers,
Nathan

  reply	other threads:[~2025-09-17  1:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 16:54 [PATCH v7 0/8] Add generated modalias to modules.builtin.modinfo Alexey Gladkov
2025-08-18 16:54 ` [PATCH v7 1/8] s390: vmlinux.lds.S: Reorder sections Alexey Gladkov
2025-08-18 16:54 ` [PATCH v7 2/8] kbuild: always create intermediate vmlinux.unstripped Alexey Gladkov
2025-09-17 11:57   ` Nicolas Schier
2025-08-18 16:54 ` [PATCH v7 3/8] kbuild: keep .modinfo section in vmlinux.unstripped Alexey Gladkov
2025-09-15  5:56   ` Nicolas Schier
2025-09-16  7:12     ` Alexey Gladkov
2025-09-16  9:36       ` Nicolas Schier
2025-09-16 11:30         ` Alexey Gladkov
2025-09-16 12:42           ` Nicolas Schier
2025-09-16 13:03             ` Alexey Gladkov
2025-09-16 13:28               ` Nicolas Schier
2025-09-17  1:10                 ` Nathan Chancellor [this message]
2025-09-17  6:49                   ` Alexey Gladkov
2025-09-17 11:55             ` Nicolas Schier
2025-09-17 12:38               ` Alexey Gladkov
2025-09-18  4:08                 ` Nicolas Schier
2025-08-18 16:54 ` [PATCH v7 4/8] kbuild: extract modules.builtin.modinfo from vmlinux.unstripped Alexey Gladkov
2025-09-17 11:57   ` Nicolas Schier
2025-08-18 16:54 ` [PATCH v7 5/8] scsi: Always define blogic_pci_tbl structure Alexey Gladkov
2025-08-18 16:55 ` [PATCH v7 6/8] modpost: Add modname to mod_device_table alias Alexey Gladkov
2025-09-14 20:07   ` Nicolas Schier
2025-08-18 16:55 ` [PATCH v7 7/8] modpost: Create modalias for builtin modules Alexey Gladkov
2025-08-18 16:55 ` [PATCH v7 8/8] kbuild: vmlinux.unstripped should always depend on .vmlinux.export.o Alexey Gladkov
2025-10-02 16:37   ` ChaosEsque Team

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=20250917011010.GA3106929@ax162 \
    --to=nathan@kernel.org \
    --cc=da.gomez@samsung.com \
    --cc=legion@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=nsc@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=samitolvanen@google.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 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).