From: Kalle Valo <kvalo@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
"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: Wed, 13 Jul 2022 10:12:58 +0300 [thread overview]
Message-ID: <87zghdmqo5.fsf@kernel.org> (raw)
In-Reply-To: <Ys3G+ZGr9k+2fTsx@bombadil.infradead.org> (Luis Chamberlain's message of "Tue, 12 Jul 2022 12:09:45 -0700")
Luis Chamberlain <mcgrof@kernel.org> writes:
> On Tue, Jul 12, 2022 at 05:57:35AM +0000, Christophe Leroy wrote:
>>
>>
>> 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 ?
>
> 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?
patchwork does not have that functionality built in, you need to enable
the bot separately:
https://korg.docs.kernel.org/patchwork/pwbot.html
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-07-13 7:13 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
2022-07-12 19:09 ` Luis Chamberlain
2022-07-13 7:12 ` Kalle Valo [this message]
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=87zghdmqo5.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=atomlin@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--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).