From: Daniel Thompson <daniel.thompson@linaro.org>
To: Aaron Tomlin <atomlin@redhat.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
christophe.leroy@csgroup.eu, hch@infradead.org, cl@linux.com,
mbenes@suse.cz, akpm@linux-foundation.org, jeyu@kernel.org,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
void@manifault.com, atomlin@atomlin.com, allen.lkml@gmail.com,
joe@perches.com, msuchanek@suse.de, oleksandr@natalenko.name,
jason.wessel@windriver.com, pmladek@suse.com
Subject: Re: [PATCH] kdb: Remove redundant module related references
Date: Fri, 11 Mar 2022 16:19:52 +0000 [thread overview]
Message-ID: <20220311161952.thugdrwd6junr7ib@maple.lan> (raw)
In-Reply-To: <20220311160153.3k2avq24mpjyrdpy@ava.usersys.com>
On Fri, Mar 11, 2022 at 04:01:53PM +0000, Aaron Tomlin wrote:
> On Fri 2022-03-11 15:47 +0000, Daniel Thompson wrote:
> > On the whole it doesn't really matter much... but landing the
> > independent parts via the normal route for kgdb code reduces what I
> > have to remember acking.
>
> Hi Daniel,
>
> Any thoughts on this [1]? Unfortunately, the wrong In-Reply-To was
> specified. So sorry about that. I will send another iteration of the series
> so that it'll be easier for Luis to apply to mcgrof/modules-testing or
> mcgrof/modules-next but after we have more feedback.
>
> [1]: https://lore.kernel.org/lkml/20220310102625.3441888-2-atomlin@redhat.com/
As above. I would rather not have to remember acking the header
changes as well... but it's not like the sky is going to fall in.
Daniel.
next prev parent reply other threads:[~2022-03-11 16:19 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 [this message]
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
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=20220311161952.thugdrwd6junr7ib@maple.lan \
--to=daniel.thompson@linaro.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=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=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;
as well as URLs for NNTP newsgroup(s).