From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH] fixup! tlsf: support on-demand requesting memory from external store
Date: Mon, 20 Oct 2025 13:04:51 +0200 [thread overview]
Message-ID: <176095829163.2400561.12455385829585675167.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251015082640.4093689-1-a.fatoum@barebox.org>
On Wed, 15 Oct 2025 10:26:39 +0200, Ahmad Fatoum wrote:
> tlsf: fix misaccounting in request_store feature
>
> A TLSF pool itself has overhead in the form of tlsf_pool_overhead()
> that's distinct from the struct pool_entry. Adding a helper that returns
> this total overhead allows us also to use roundup_pow_of_two(), which
> previously issues a warning on clang about sizeof(sizeof(...)) looking
> strange.
>
> [...]
Applied, thanks!
[1/1] fixup! tlsf: support on-demand requesting memory from external store
https://git.pengutronix.de/cgit/barebox/commit/?id=78cd84652672 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-10-20 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 8:26 Ahmad Fatoum
2025-10-20 11:04 ` Sascha Hauer [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=176095829163.2400561.12455385829585675167.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.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