linux-kernel - Re: [PATCH 1/2] mcb: Add missing modpost build support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHp75VeNtYJPmXtDfWEN3a184YXTKNems657UDeBKp4xpOGovQ@mail.gmail.com>
Date: Thu, 27 Nov 2025 18:10:33 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@...gon.com>
Cc: linus.walleij@...aro.org, brgl@...nel.org, jic23@...nel.org, 
	dlechner@...libre.com, nuno.sa@...log.com, andy@...nel.org, 
	gregkh@...uxfoundation.org, jirislaby@...nel.org, morbidrsa@...il.com, 
	jth@...nel.org, wim@...ux-watchdog.org, linux@...ck-us.net, nathan@...nel.org, 
	nsc@...nel.org, linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org, 
	linux-iio@...r.kernel.org, linux-serial@...r.kernel.org, 
	linux-watchdog@...r.kernel.org, linux-kbuild@...r.kernel.org, 
	Jorge Sanjuan Garcia <dev-jorge.sanjuangarcia@...gon.com>
Subject: Re: [PATCH 1/2] mcb: Add missing modpost build support

On Thu, Nov 27, 2025 at 5:56 PM Jose Javier Rodriguez Barbarin
<dev-josejavier.rodriguez@...gon.com> wrote:
>
> mcb bus is not prepared to autoload client drivers with the data defined on
> the drivers' MODULE_DEVICE_TABLE. modpost cannot access to mcb_table_id
> inside MODULE_DEVICE_TABLE so the data declared inside is ignored.
>
> Add modpost build support for accessing to the mcb_table_id coded on device
> drivers' MODULE_DEVICE_TABLE.

...

>  static const struct devtable devtable[] = {

>         {"cpu", SIZE_cpu_feature, do_cpu_entry},
>         {"mei", SIZE_mei_cl_device_id, do_mei_entry},
>         {"rapidio", SIZE_rio_device_id, do_rio_entry},
> +       {"mcb", SIZE_mcb_device_id, do_mcb_entry},

Perhaps squeeze it to be more ordered (yes, I know that the table is
not so ordered, but given context suggests to put it after "mei").

>         {"ulpi", SIZE_ulpi_device_id, do_ulpi_entry},
>         {"hdaudio", SIZE_hda_device_id, do_hda_entry},
>         {"sdw", SIZE_sdw_device_id, do_sdw_entry},



-- 
With Best Regards,
Andy Shevchenko