From: Luis Chamberlain <mcgrof@kernel.org>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Aaron Tomlin <atomlin@redhat.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
cl@linux.com, pmladek@suse.com, mbenes@suse.cz,
akpm@linux-foundation.org, jeyu@kernel.org,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
live-patching@vger.kernel.org, atomlin@atomlin.com,
ghalat@redhat.com, allen.lkml@gmail.com, void@manifault.com,
joe@perches.com
Subject: Re: [RFC PATCH v4 00/13] module: core code clean up
Date: Thu, 3 Feb 2022 12:13:03 -0800 [thread overview]
Message-ID: <Yfw3T22UyE2oyTuY@bombadil.infradead.org> (raw)
In-Reply-To: <20220203194317.GC3113@kunlun.suse.cz>
On Thu, Feb 03, 2022 at 08:43:17PM +0100, Michal Suchánek wrote:
> Hello,
>
> On Wed, Feb 02, 2022 at 04:20:41PM -0800, Luis Chamberlain wrote:
> > On Sun, Jan 30, 2022 at 09:32:01PM +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 branch mcgrof/modules-next since a97ac8cb24a3/or
> > > modules-5.17-rc1. Please let me know your thoughts.
> > >
> > > Changes since v1 [2]:
> >
> > Thanks for all this work Aaron! Can you drop the RFC prefix,
> > rebase onto linus' latest tree (as he already merged my
> > modules-next, so his tree is more up to date), and submit again?
> >
> > I'll then apply this to my modules-next, and then ask Christophe to
> > rebase on top of that.
> >
> > Michal, you'd be up next if you want to go through modules-next.
>
> Sounds like a good idea. When rebasing on top of 5.17-rc1 the only
> conflict was on the module code.
I'll let you know once modules-next is ready for your code. But before
that, does anyone have any objections with this code going through
modules-next? Although its kexec related it touches on a lot of
kernel/module.c and if we don't take it on modules-next I'm afraid
there will be quite a bit of conflicts there later.
Luis
next prev parent reply other threads:[~2022-02-03 20:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 21:32 [RFC PATCH v4 00/13] module: core code clean up Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 01/13] module: Move all into module/ Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 02/13] module: Simple refactor in preparation for split Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 03/13] module: Move livepatch support to a separate file Aaron Tomlin
2022-02-08 11:42 ` Petr Mladek
2022-02-08 15:18 ` Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 04/13] module: Move latched RB-tree " Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 05/13] module: Move arch strict rwx " Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 06/13] module: Move " Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 07/13] module: Move extra signature support out of core code Aaron Tomlin
2022-02-09 14:28 ` Miroslav Benes
2022-02-09 14:37 ` Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 08/13] module: Move kmemleak support to a separate file Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 09/13] module: Move kallsyms support into " Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 10/13] module: Move procfs " Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 11/13] module: Move sysfs " Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 12/13] module: Move kdb_modules list out of core code Aaron Tomlin
2022-01-30 21:32 ` [RFC PATCH v4 13/13] module: Move version support into a separate file Aaron Tomlin
2022-02-01 16:44 ` [RFC PATCH v4 00/13] module: core code clean up Allen
2022-02-05 20:33 ` Aaron Tomlin
2022-02-02 2:44 ` Luis Chamberlain
2022-02-06 14:40 ` Aaron Tomlin
2022-02-03 0:20 ` Luis Chamberlain
2022-02-03 7:48 ` Christophe Leroy
2022-02-06 14:45 ` Aaron Tomlin
2022-02-03 18:01 ` Christophe Leroy
2022-02-06 16:54 ` Aaron Tomlin
2022-02-07 16:46 ` Aaron Tomlin
2022-02-07 17:17 ` Christophe Leroy
2022-02-07 18:01 ` Aaron Tomlin
2022-02-08 7:50 ` Christophe Leroy
2022-02-08 10:05 ` Aaron Tomlin
2022-02-03 18:15 ` Christophe Leroy
2022-02-06 16:57 ` Aaron Tomlin
2022-02-03 19:43 ` Michal Suchánek
2022-02-03 20:13 ` Luis Chamberlain [this message]
2022-02-03 20:10 ` Luis Chamberlain
2022-02-06 17:00 ` Aaron Tomlin
2022-02-06 14:42 ` Aaron Tomlin
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=Yfw3T22UyE2oyTuY@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=atomlin@atomlin.com \
--cc=atomlin@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=cl@linux.com \
--cc=ghalat@redhat.com \
--cc=jeyu@kernel.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=msuchanek@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).