On Tue, Jul 12, 2022 at 05:57:35AM +0000, Christophe Leroy wrote:

Le 11/07/2022 à 21:07, Luis Chamberlain a écrit :

quoted

On Mon, Jul 11, 2022 at 06:33:08PM +0000, Christophe Leroy wrote:

quoted

Le 11/07/2022 à 18:20, Luis Chamberlain a écrit :

quoted

This moves all the module symbols from init/Kconfig to its
own dedicated file now that we have all of the module code in
its own directory.

This does not introduce any functional changes.

Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

It is similar to the patch I sent in February, isn't it ?
(https://patchwork.kernel.org/project/linux-modules/patch/4042712961d42186c449734c253511ea7076c780.1645543105.git.christophe.leroy@csgroup.eu/)

Sorry, I had missed that. Can you send a new v2 based on today's
modules-next? And I'll just drop my patch?

I sent out v2 rebased on today's modules-next 
(c76654e22da1e0cb830bd0eb5832072fb76df358)

I see all my patches still have status 'new' in modules's patchwork 
(https://patchwork.kernel.org/project/linux-modules/list/?submitter=192363).

Don't you maintain it ?

Yes but I never knew we used to have patchwork for modules, but glad we have
that now. Anyway all your patches are applied, is patchwork dumb to not
pick that up?

  Luis