From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Luis Chamberlain <mcgrof@kernel.org>, Aaron Tomlin <atomlin@redhat.com>
Cc: "cl@linux.com" <cl@linux.com>, "mbenes@suse.cz" <mbenes@suse.cz>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"jeyu@kernel.org" <jeyu@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
"void@manifault.com" <void@manifault.com>,
"atomlin@atomlin.com" <atomlin@atomlin.com>,
"allen.lkml@gmail.com" <allen.lkml@gmail.com>,
"joe@perches.com" <joe@perches.com>,
"msuchanek@suse.de" <msuchanek@suse.de>,
"oleksandr@natalenko.name" <oleksandr@natalenko.name>,
"jason.wessel@windriver.com" <jason.wessel@windriver.com>,
"daniel.thompson@linaro.org" <daniel.thompson@linaro.org>,
"hch@infradead.org" <hch@infradead.org>,
"pmladek@suse.com" <pmladek@suse.com>,
Lucas De Marchi <lucas.de.marchi@gmail.com>
Subject: Re: [PATCH v10 00/14] module: core code clean up
Date: Tue, 8 Mar 2022 06:10:56 +0000 [thread overview]
Message-ID: <1245a265-e3c0-b52a-5fc4-9508f5dd211e@csgroup.eu> (raw)
In-Reply-To: <YiZzotNHdKsvixLD@bombadil.infradead.org>
Hi Luis,
Le 07/03/2022 à 22:05, Luis Chamberlain a écrit :
> On Mon, Mar 07, 2022 at 05:44:55PM +0000, Aaron Tomlin wrote:
>> Hi Luis,
>>
>> As per your suggestion [1], this is an attempt to refactor and split
>> optional code out of core module support code into separate components.
>> This version is based on Linus' commit 7993e65fdd0f ("Merge tag
>> 'mtd/fixes-for-5.17-rc5' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux").
>
> Thanks! Pushed out to modules-testing to see what 0-day can find.
> Further review from others is welcomed in the meantime. If no issues
> are found, we also get kmod testing done, and more reviews, I can
> push then later to modules-next for further testing on linux-next.
>
As far as I understood kmod testing doesn't test the kernel at all so it
won't test any of our changes.
In his mail last week, Lucas said: "kmod's testsuite don't test anything
on the kernel side... the kernel part is mocked by the testsuite itself."
Christophe
prev parent reply other threads:[~2022-03-08 6:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 17:44 [PATCH v10 00/14] module: core code clean up Aaron Tomlin
2022-03-07 17:44 ` [PATCH v10 01/14] module: Move all into module/ Aaron Tomlin
2022-03-07 17:44 ` [PATCH v10 02/14] module: Simple refactor in preparation for split Aaron Tomlin
2022-03-07 17:44 ` [PATCH v10 03/14] module: Make internal.h and decompress.c more compliant Aaron Tomlin
2022-03-07 17:44 ` [PATCH v10 04/14] module: Move livepatch support to a separate file Aaron Tomlin
2022-03-07 17:45 ` [PATCH v10 05/14] module: Move latched RB-tree " Aaron Tomlin
2022-03-07 17:45 ` [PATCH v10 06/14] module: Move strict rwx " Aaron Tomlin
2022-03-07 17:45 ` [PATCH v10 07/14] module: Move extra signature support out of core code Aaron Tomlin
2022-03-07 17:45 ` [PATCH v10 08/14] module: Move kmemleak support to a separate file Aaron Tomlin
2022-03-07 17:45 ` [PATCH v10 09/14] module: Move kallsyms support into " Aaron Tomlin
2022-03-07 17:45 ` [PATCH v10 10/14] module: kallsyms: Fix suspicious rcu usage Aaron Tomlin
2022-03-07 17:45 ` [PATCH v10 11/14] module: Move procfs support into a separate file Aaron Tomlin
2022-03-07 17:47 ` [PATCH v10 12/14] module: Move sysfs " Aaron Tomlin
2022-03-07 17:47 ` [PATCH v10 13/14] module: Move kdb module related code out of main kdb code Aaron Tomlin
2022-03-08 8:36 ` Christophe Leroy
2022-03-08 10:51 ` Aaron Tomlin
2022-03-08 10:52 ` [PATCH] kdb: Remove redundant module related references Aaron Tomlin
2022-03-09 12:06 ` Daniel Thompson
2022-03-10 9:20 ` Aaron Tomlin
2022-03-10 21:07 ` Luis Chamberlain
2022-03-11 15:47 ` Daniel Thompson
2022-03-11 16:01 ` Aaron Tomlin
2022-03-11 16:19 ` Daniel Thompson
2022-03-07 17:47 ` [PATCH v10 14/14] module: Move version support into a separate file Aaron Tomlin
2022-03-07 21:05 ` [PATCH v10 00/14] module: core code clean up Luis Chamberlain
2022-03-08 6:10 ` Christophe Leroy [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=1245a265-e3c0-b52a-5fc4-9508f5dd211e@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=atomlin@atomlin.com \
--cc=atomlin@redhat.com \
--cc=cl@linux.com \
--cc=daniel.thompson@linaro.org \
--cc=hch@infradead.org \
--cc=jason.wessel@windriver.com \
--cc=jeyu@kernel.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=msuchanek@suse.de \
--cc=oleksandr@natalenko.name \
--cc=pmladek@suse.com \
--cc=void@manifault.com \
/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