mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Aaron Tomlin <atomlin@redhat.com>,
	"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] Miscellaneous cleanups
Date: Wed, 23 Feb 2022 06:34:34 +0000	[thread overview]
Message-ID: <f0c560b4-6f71-63c3-8cb4-1570f0ec42b2@csgroup.eu> (raw)
In-Reply-To: <YhV/ZQKsO2rElYdL@bombadil.infradead.org>



Le 23/02/2022 à 01:27, Luis Chamberlain a écrit :
> On Tue, Feb 22, 2022 at 04:16:30PM +0100, Christophe Leroy wrote:
>> This series applies on top of my series "Allocate module text and data separately" v5.
>>
>> It does some cleanup around the settling of modules's layout page flags:
>> - Make module_enable_x() independent of CONFIG_ARCH_HAS_STRICT_MODULE_RWX
>> - Reunify everything into strict_rwx.c
>> - Change big hammer BUG_ON()s into WARN_ON()s
>> - Change misleading debug_align() to strict_align()
>>
>> Changes in v2/v3:
>> - Rebased on top of my series "Allocate module text and data separately" v5
>> - Moved the Kconfig patch out of this series, it is an independent change
>>
>> Sorry for the mess in v2.
> 
> Thanks for all this work! Any chance you can actually submit this prior
> to your allocate module series? This and the patch, "module: Move
> module's Kconfig item in kernel/module/". Because *iff* we get enough
> testing out of Aaron's changes and your cleanups, perhaps those might
> be candidates for the next merge window. Then we can save all the new
> functional changes for the other merge window.
> 

Sure I can switch the two series.

The Kconfig patch is independant, you can already apply it in any order, 
I won't resend unless I get comments on it.

Christophe

      reply	other threads:[~2022-02-23  6:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 15:16 Christophe Leroy
2022-02-22 15:16 ` [PATCH v3 1/4] module: Make module_enable_x() independent of CONFIG_ARCH_HAS_STRICT_MODULE_RWX Christophe Leroy
2022-02-22 15:16 ` [PATCH v3 2/4] module: Move module_enable_x() and frob_text() in strict_rwx.c Christophe Leroy
2022-02-22 15:16 ` [PATCH v3 3/4] module: Rework layout alignment to avoid BUG_ON()s Christophe Leroy
2022-02-22 15:16 ` [PATCH v3 4/4] module: Rename debug_align() as strict_align() Christophe Leroy
2022-02-23  0:27 ` [PATCH v3 0/4] Miscellaneous cleanups Luis Chamberlain
2022-02-23  6:34   ` 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=f0c560b4-6f71-63c3-8cb4-1570f0ec42b2@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=atomlin@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.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

all inboxes | Powered by JetHome®