From: Vlastimil Babka <vbabka@suse.cz>
To: Petr Tesarik <ptesarik@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Harry Yoo <harry.yoo@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] slab: switch away from the legacy param parser
Date: Mon, 27 Oct 2025 16:06:21 +0100 [thread overview]
Message-ID: <2236fdb6-4616-4b9f-82c9-eba3ce5d371f@suse.cz> (raw)
In-Reply-To: <cover.1761324765.git.ptesarik@suse.com>
On 10/24/25 19:06, Petr Tesarik wrote:
> The handling of legacy __setup() parameters has some confusing quirks.
> Instead of fixing them, convert the code to struct kerenel_param, which
> is a saner API.
>
> Note that parameters defined with core_param() and __core_param_cb() are
> parsed early in start_kernel(). Do not confuse them with core_param_cb(),
> which are processed at a later stage.
Thanks! Added to slab/for-next
> Petr Tesarik (3):
> slab: constify slab debug strings
> slab: convert setup_slub_debug() to use __core_param_cb()
> slab: use core_param for remaining command line parameters
>
> mm/slub.c | 87 ++++++++++++++++++++++++++++++++-----------------------
> 1 file changed, 51 insertions(+), 36 deletions(-)
>
next prev parent reply other threads:[~2025-10-27 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 17:06 Petr Tesarik
2025-10-24 17:06 ` [PATCH 1/3] slab: constify slab debug strings Petr Tesarik
2025-10-24 17:44 ` Christoph Lameter (Ampere)
2025-10-29 9:54 ` Harry Yoo
2025-10-24 17:06 ` [PATCH 2/3] slab: convert setup_slub_debug() to use __core_param_cb() Petr Tesarik
2025-10-29 10:16 ` Harry Yoo
2025-10-24 17:06 ` [PATCH 3/3] slab: use new API for remaining command line parameters Petr Tesarik
2025-10-29 10:52 ` Harry Yoo
2025-10-30 13:32 ` Petr Tesarik
2025-10-30 13:35 ` Vlastimil Babka
2025-10-27 15:06 ` Vlastimil Babka [this message]
2025-10-30 11:36 ` [PATCH 0/3] slab: switch away from the legacy param parser Petr Tesarik
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=2236fdb6-4616-4b9f-82c9-eba3ce5d371f@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ptesarik@suse.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
/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