From: Mike Rapoport <rppt@kernel.org>
To: linux-mm@kvack.org, "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: Mike Rapoport <rppt@kernel.org>,
linux-kernel@vger.kernel.org, kernel-dev@igalia.com,
kernel@gpiccoli.net, Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
SeongJae Park <sj@kernel.org>
Subject: Re: [PATCH v3 0/2] Small improvements to reserve_mem, 3rd attempt
Date: Tue, 24 Mar 2026 17:17:17 +0200 [thread overview]
Message-ID: <177436539808.216951.5818644447126905972.b4-ty@b4> (raw)
In-Reply-To: <20260318190816.1811325-1-gpiccoli@igalia.com>
On Wed, 18 Mar 2026 15:56:31 -0300, Guilherme G. Piccoli wrote:
> tl; dr: we are adding here error messages in case of failures when
> reserve_mem parameter is used, and also a debugfs file to show
> successful reservations, with name and size as passed in the cmdline.
>
> More details and history, please take a look at:
>
> V2: lore.kernel.org/r/20260304203300.1414286-2-gpiccoli@igalia.com/
> V1: lore.kernel.org/r/20260217195816.861684-1-gpiccoli@igalia.com/
>
> [...]
Applied to for-next branch of memblock.git tree, thanks!
[1/2] mm/memblock: Print out errors on reserve_mem parser
commit: 855b388182df35d2907cb2d5723270b0df3a9e6e
[2/2] mm/memblock: Add reserve_mem debugfs info
commit: 2db6cd07805051744036235f7ee9f24a9be9e283
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
branch: for-next
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-03-24 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 18:56 [PATCH v3 0/2] Small improvements to reserve_mem, 3rd attempt Guilherme G. Piccoli
2026-03-18 18:56 ` [PATCH v3 1/2] mm/memblock: Print out errors on reserve_mem parser Guilherme G. Piccoli
2026-03-18 18:56 ` [PATCH v3 2/2] mm/memblock: Add reserve_mem debugfs info Guilherme G. Piccoli
2026-03-19 16:34 ` Mike Rapoport
2026-03-19 17:14 ` Guilherme G. Piccoli
2026-03-19 18:01 ` Mike Rapoport
2026-03-24 1:22 ` [PATCH v4 1/2] mm/memblock: Print out errors on reserve_mem parser Guilherme G. Piccoli
2026-03-24 1:22 ` [PATCH v4 2/2] mm/memblock: Add reserve_mem debugfs info Guilherme G. Piccoli
2026-03-25 1:24 ` SeongJae Park
2026-03-24 15:17 ` Mike Rapoport [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=177436539808.216951.5818644447126905972.b4-ty@b4 \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gpiccoli@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rostedt@goodmis.org \
--cc=sj@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