From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>, Song Liu <song@kernel.org>
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@lst.de, kernel-team@meta.com,
Luis Chamberlain <mcgrof@kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [PATCH v4] module: replace module_layout with module_memory
Date: Tue, 31 Jan 2023 17:11:03 +0100 [thread overview]
Message-ID: <87zg9yznu0.ffs@tglx> (raw)
In-Reply-To: <Y9j9Svys7eb9E2Mh@hirez.programming.kicks-ass.net>
On Tue, Jan 31 2023 at 12:36, Peter Zijlstra wrote:
> On Mon, Jan 30, 2023 at 10:21:09AM -0800, Song Liu wrote:
>> This is the preparation work for the type aware module_alloc() discussed
>> in [1]. While this work is not covered much in the discussion, it is a
>> critical step of the effort.
>>
>> As this part grows pretty big (~1000 lines, + and -), I would like get
>> some feedback on it, so that I know it is on the right track.
>>
>> Please share your comments. Thanks!
>
> Aside from the things already reported I like where this is going.
Agreed.
tglx
prev parent reply other threads:[~2023-01-31 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 18:21 [PATCH v4] module: replace module_layout with module_memory Song Liu
2023-01-31 9:09 ` Peter Zijlstra
2023-01-31 10:58 ` Christophe Leroy
2023-01-31 12:04 ` Peter Zijlstra
2023-01-31 12:14 ` Christophe Leroy
2023-01-31 14:06 ` Peter Zijlstra
2023-01-31 17:41 ` Christophe Leroy
2023-01-31 11:14 ` Peter Zijlstra
2023-02-01 0:37 ` Song Liu
2023-01-31 11:26 ` Peter Zijlstra
2023-01-31 11:36 ` Peter Zijlstra
2023-01-31 16:11 ` Thomas Gleixner [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=87zg9yznu0.ffs@tglx \
--to=tglx@linutronix.de \
--cc=christophe.leroy@csgroup.eu \
--cc=hch@lst.de \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mcgrof@kernel.org \
--cc=peterz@infradead.org \
--cc=song@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 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.