Re: [PATCH v9 4/8] kallsyms: introduce sections needed to map symbols to built-in modules

From: Luis Chamberlain
Date: Sat Nov 12 2022 - 22:15:51 EST

Next message: Luis Chamberlain: "Re: [PATCH v9 7/8] kallsyms: add /proc/kallmodsyms for text symbol disambiguation"
Previous message: Luis Chamberlain: "Re: [PATCH v9 3/8] kbuild: generate an address ranges map at vmlinux link time"
In reply to: Nick Alcock: "[PATCH v9 4/8] kallsyms: introduce sections needed to map symbols to built-in modules"
Next in thread: Nick Alcock: "Re: [PATCH v9 4/8] kallsyms: introduce sections needed to map symbols to built-in modules"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Nov 09, 2022 at 01:41:28PM +0000, Nick Alcock wrote:
> The mapping consists of three new symbols

The entire commit log does not describe *why*.

Can I also trouble you to rebase on top of modules-next [0]

Does the kallsyms loop more than 3 times now with Zhen Lei's work and
your new symbols on top on a allyesconfig build?

[0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=modules-next

Luis

Next message: Luis Chamberlain: "Re: [PATCH v9 7/8] kallsyms: add /proc/kallmodsyms for text symbol disambiguation"
Previous message: Luis Chamberlain: "Re: [PATCH v9 3/8] kbuild: generate an address ranges map at vmlinux link time"
In reply to: Nick Alcock: "[PATCH v9 4/8] kallsyms: introduce sections needed to map symbols to built-in modules"
Next in thread: Nick Alcock: "Re: [PATCH v9 4/8] kallsyms: introduce sections needed to map symbols to built-in modules"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]