From: Luis Chamberlain <mcgrof@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linux-arch@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Aaron Tomlin <atomlin@redhat.com>,
linuxppc-dev@lists.ozlabs.org, linux-modules@vger.kernel.org
Subject: Re: [PATCH v6 0/6] Allocate module text and data separately
Date: Tue, 22 Mar 2022 10:24:33 -0700 [thread overview]
Message-ID: <YjoGUfHa1WgYWiR1@bombadil.infradead.org> (raw)
In-Reply-To: <cover.1645607143.git.christophe.leroy@csgroup.eu>
On Wed, Feb 23, 2022 at 01:02:10PM +0100, Christophe Leroy wrote:
> This series applies on top of my series "miscellanuous cleanups" v4.
Queued onto modules-testing! BTW I just had to rebase the change
with the kdb changes, it was a trivial change.
Luis
prev parent reply other threads:[~2022-03-22 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 12:02 [PATCH v6 0/6] Allocate module text and data separately Christophe Leroy
2022-02-23 12:02 ` [PATCH v6 1/6] module: Always have struct mod_tree_root Christophe Leroy
2022-02-23 12:02 ` [PATCH v6 2/6] module: Prepare for handling several RB trees Christophe Leroy
2022-02-23 12:02 ` [PATCH v6 3/6] module: Introduce data_layout Christophe Leroy
2022-02-23 12:02 ` [PATCH v6 4/6] module: Add CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC Christophe Leroy
2022-02-23 12:02 ` [PATCH v6 5/6] module: Remove module_addr_min and module_addr_max Christophe Leroy
2022-02-23 12:02 ` [PATCH v6 6/6] powerpc: Select ARCH_WANTS_MODULES_DATA_IN_VMALLOC on book3s/32 and 8xx Christophe Leroy
2022-03-22 17:24 ` Luis Chamberlain [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=YjoGUfHa1WgYWiR1@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=atomlin@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-modules@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).