From: Tom Rini <trini@konsulko.com>
To: Cole Munz <Munzzyy1@proton.me>
Cc: u-boot@lists.u-boot-project.org, Alexey Charkov <alchark@flipper.net>
Subject: Re: [PATCH] lib: zstd: update to latest Linux zstd 1.5.7
Date: Fri, 14 Aug 2026 15:06:46 -0600 [thread overview]
Message-ID: <20260814210646.GL3297518@bill-the-cat> (raw)
In-Reply-To: <259e9abc-603d-4a07-bd6f-41b357abef49@proton.me>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
On Fri, Aug 14, 2026 at 07:43:18PM +0000, Cole Munz wrote:
> Thanks for the qconfig pointer. It caught a mistake in what I sent.
>
> The count is 47, not 41. My scan followed #include of .config fragments but
> not defconfigs that include another defconfig. That missed am6254atl_evm_a53,
> am62px_evm_a53_ethboot, am62x_evm_a53_ethboot, am62x_lpsk_a53 and
> sandbox64_lwip.
>
> qconfig -f ZSTD reports 43 here. The other four are sandbox_nocmdline,
> th1520_lpi4a, turris_1x_nor and turris_1x_sdcard. They are missing from my
> qconfig.db because 234 boards failed to configure without RISC-V and PowerPC
> toolchains. Treat 47 as a floor until that database is built with a full
> toolchain set.
>
> Size numbers are unaffected. Those five are AM62x and sandbox variants. Both
> families are already in the table.
The important thing isn't just the numbers, but what buildman gives (and
bloat-o-meter for example didn't last I knew) was really good answers to
where the growth is. Which makes it easier to sometimes ask why, and
then work to reduce it.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-14 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 1:57 [PATCH] lib: zstd: update to latest Linux zstd 1.5.7 Cole Munz
2026-08-14 18:34 ` Cole Munz
2026-08-14 18:53 ` Tom Rini
2026-08-14 19:43 ` Cole Munz
2026-08-14 21:06 ` Tom Rini [this message]
2026-08-14 22:37 ` Cole Munz
2026-08-14 23:20 ` Tom Rini
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=20260814210646.GL3297518@bill-the-cat \
--to=trini@konsulko.com \
--cc=Munzzyy1@proton.me \
--cc=alchark@flipper.net \
--cc=u-boot@lists.u-boot-project.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