linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: "linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"atomlin@redhat.com" <atomlin@redhat.com>
Subject: Re: [PATCH] modules: move module symbols from init/Kconfig
Date: Tue, 12 Jul 2022 05:57:35 +0000	[thread overview]
Message-ID: <09f3ec9a-3a8e-d116-d38a-2fdb55f125c6@csgroup.eu> (raw)
In-Reply-To: <Ysx1C9IkJiFL+OH5@bombadil.infradead.org>



Le 11/07/2022 à 21:07, Luis Chamberlain a écrit :
> On Mon, Jul 11, 2022 at 06:33:08PM +0000, Christophe Leroy wrote:
>>
>>
>> Le 11/07/2022 à 18:20, Luis Chamberlain a écrit :
>>> 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 ?

Thanks
Christophe

  reply	other threads:[~2022-07-12  5:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 16:20 [PATCH] modules: move module symbols from init/Kconfig Luis Chamberlain
2022-07-11 18:33 ` Christophe Leroy
2022-07-11 19:07   ` Luis Chamberlain
2022-07-12  5:57     ` Christophe Leroy [this message]
2022-07-12 19:09       ` Luis Chamberlain
2022-07-13  7:12         ` Kalle Valo

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=09f3ec9a-3a8e-d116-d38a-2fdb55f125c6@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=atomlin@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    /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).