From: Luis Chamberlain <mcgrof@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Aaron Tomlin <atomlin@redhat.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
"cl@linux.com" <cl@linux.com>,
"pmladek@suse.com" <pmladek@suse.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>,
"live-patching@vger.kernel.org" <live-patching@vger.kernel.org>,
"atomlin@atomlin.com" <atomlin@atomlin.com>,
"ghalat@redhat.com" <ghalat@redhat.com>,
"allen.lkml@gmail.com" <allen.lkml@gmail.com>,
"void@manifault.com" <void@manifault.com>,
"msuchanek@suse.de" <msuchanek@suse.de>,
"oleksandr@natalenko.name" <oleksandr@natalenko.name>
Subject: Re: [PATCH v5 01/13] module: Move all into module/
Date: Thu, 10 Feb 2022 10:50:58 -0800 [thread overview]
Message-ID: <YgVekoAxiV5nw22q@bombadil.infradead.org> (raw)
In-Reply-To: <926e5c35d50ec5f6d7e789831be96744ca8d6423.camel@perches.com>
On Thu, Feb 10, 2022 at 09:02:09AM -0800, Joe Perches wrote:
> On Thu, 2022-02-10 at 14:45 +0000, Aaron Tomlin wrote:
> > On Thu 2022-02-10 11:11 +0000, Christophe Leroy wrote:
> > > > diff --git a/MAINTAINERS b/MAINTAINERS
> []
> > > > @@ -13001,7 +13001,7 @@ L: linux-kernel@vger.kernel.org
> > > > S: Maintained
> > > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git modules-next
> > > > F: include/linux/module.h
> > > > -F: kernel/module.c
> > > > +F: kernel/module/main.c
> > >
> > > Shouldn't it be the entire directory ?
> >
> > Indeed it should. Moving forward: kernel/module/*
>
> Better would be:
>
> F: kernel/module/
>
> in case it ever gets subdirectories too.
Yes, that also later allows us to add entries for things like say
livepatching. Or we peg the livepatching file to the livepatching
tag. Either way, one of the side goals of the split is to eventually
help scale maintenance.
Luis
next prev parent reply other threads:[~2022-02-10 18:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 17:03 [PATCH v5 00/13] module: core code clean up Aaron Tomlin
2022-02-09 17:03 ` [PATCH v5 01/13] module: Move all into module/ Aaron Tomlin
2022-02-10 11:11 ` Christophe Leroy
2022-02-10 14:45 ` Aaron Tomlin
2022-02-10 17:02 ` Joe Perches
2022-02-10 17:22 ` Aaron Tomlin
2022-02-10 18:50 ` Luis Chamberlain [this message]
2022-02-09 17:03 ` [PATCH v5 02/13] module: Simple refactor in preparation for split Aaron Tomlin
2022-02-10 11:18 ` Christophe Leroy
2022-02-10 16:26 ` Aaron Tomlin
2022-02-09 17:03 ` [PATCH v5 03/13] module: Make internal.h more compliant Aaron Tomlin
2022-02-10 11:20 ` Christophe Leroy
2022-02-09 17:03 ` [PATCH v5 04/13] module: Move livepatch support to a separate file Aaron Tomlin
2022-02-09 18:51 ` Christophe Leroy
2022-02-10 11:44 ` Christophe Leroy
2022-02-10 17:20 ` Aaron Tomlin
2022-02-09 17:03 ` [PATCH v5 05/13] module: Move latched RB-tree " Aaron Tomlin
2022-02-10 12:03 ` Christophe Leroy
2022-02-10 22:41 ` Aaron Tomlin
2022-02-09 17:03 ` [PATCH v5 06/13] module: Move strict rwx " Aaron Tomlin
2022-02-10 12:21 ` Christophe Leroy
2022-02-11 11:09 ` 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=YgVekoAxiV5nw22q@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.