public inbox for linux-modules@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Alexey Gladkov <legion@kernel.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Nicolas Schier <nicolas.schier@linux.dev>,
	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
Subject: Re: [PATCH v6 3/9] kbuild: extract modules.builtin.modinfo from vmlinux.unstripped
Date: Sun, 17 Aug 2025 23:43:41 -0700	[thread overview]
Message-ID: <20250818064341.GA2815827@ax162> (raw)
In-Reply-To: <aKHQl_XC63-c-81L@example.org>

On Sun, Aug 17, 2025 at 02:52:39PM +0200, Alexey Gladkov wrote:
> My emails must have gotten lost somewhere. Because I replied to that
> message right away and provided a fix. Stephen even applied it to the tree
> later. You were in CC whole time.
> 
> https://lore.kernel.org/all/20250730090025.2402129-1-legion@kernel.org/
> 
> Tomorrow I will make a new version with the corrections I missed. But now,
> I'm not sure to which tree I should send it.

You can send it against kbuild-next:

https://git.kernel.org/kbuild/l/kbuild-next

Cheers,
Nathan

  reply	other threads:[~2025-08-18  6:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 13:07 [PATCH v6 0/9] Add generated modalias to modules.builtin.modinfo Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 1/9] kbuild: always create intermediate vmlinux.unstripped Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 2/9] kbuild: keep .modinfo section in vmlinux.unstripped Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 3/9] kbuild: extract modules.builtin.modinfo from vmlinux.unstripped Alexey Gladkov
2025-08-17 12:34   ` Masahiro Yamada
2025-08-17 12:52     ` Alexey Gladkov
2025-08-18  6:43       ` Nathan Chancellor [this message]
2025-08-14 13:07 ` [PATCH v6 4/9] scsi: Always define blogic_pci_tbl structure Alexey Gladkov
2025-08-19  2:04   ` Martin K. Petersen
2025-08-19  7:18     ` Nathan Chancellor
2025-08-20  1:52       ` Martin K. Petersen
2025-08-20 16:11         ` Nathan Chancellor
2025-08-25 10:09           ` Alexey Gladkov
2025-08-25 16:56             ` Nathan Chancellor
2025-08-14 13:07 ` [PATCH v6 5/9] pinctrl: meson: Fix typo in device table macro Alexey Gladkov
2025-08-18  9:11   ` Linus Walleij
2025-08-14 13:07 ` [PATCH v6 6/9] modpost: Add modname to mod_device_table alias Alexey Gladkov
2025-08-14 13:26   ` Danilo Krummrich
2025-08-14 13:54     ` Alexey Gladkov
2025-08-14 14:03       ` Danilo Krummrich
2025-08-14 21:46         ` Alexey Gladkov
2025-08-14 22:17           ` Danilo Krummrich
2025-08-14 13:07 ` [PATCH v6 7/9] modpost: Create modalias for builtin modules Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 8/9] kbuild: vmlinux.unstripped should always depend on .vmlinux.export.o Alexey Gladkov
2025-08-14 13:07 ` [PATCH v6 9/9] s390: vmlinux.lds.S: Reorder sections Alexey Gladkov
2025-08-14 14:16   ` Heiko Carstens
2025-08-14 21:51     ` Alexey Gladkov

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=20250818064341.GA2815827@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=nicolas.schier@linux.dev \
    --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