public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: lukas.funke-oss@weidmueller.com
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Lukas Funke <lukas.funke@weidmueller.com>,
	Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH v3 07/11] lib: vsprintf: enable '%pbl' format specifier
Date: Thu, 18 Jan 2024 15:22:43 -0500	[thread overview]
Message-ID: <20240118202243.GF12635@bill-the-cat> (raw)
In-Reply-To: <20240110091037.392520-8-lukas.funke-oss@weidmueller.com>

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

On Wed, Jan 10, 2024 at 10:10:33AM +0100, lukas.funke-oss@weidmueller.com wrote:

> From: Lukas Funke <lukas.funke@weidmueller.com>
> 
> The commit enables vsprintf() to handle the '%pbl' format specifier
> in order to print bitmaps and its derivatives such as cpumask and
> nodemask [1]. This can be used to derive kernel boot parameters from
> bitmaks such as 'isolcpu' or 'nohz_full' [2].
> 
> [1] https://www.kernel.org/doc/Documentation/printk-formats.txt
> [2] https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
> 
> Signed-off-by: Lukas Funke <lukas.funke@weidmueller.com>

This breaks building ARC platforms, and possibly others.  Note that
tools/buildman/buildman is happy to fetch toolchains for you, and in
this case it's also just the current kernel.org cross-toolchain. Please
see https://docs.u-boot.org/en/latest/develop/ci_testing.html about how
to trigger a CI run prior to sending v4, thanks.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-01-18 20:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10  9:10 [PATCH v3 00/11] Enable setexpr command to print cpu-list like bitmaps lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 01/11] sandbox: add generic find_next_zero_bit implementation lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 02/11] linux: bitmap.h: add 'for_each_set_bitrange' iteration macro lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 03/11] test: cmd: setexpr: Add tests for bitmap string format lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 04/11] doc: printf() codes: Add bitmap format specifier lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 05/11] cmd: printf: Correctly handle field width lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 06/11] lib: Add hextobarray() function lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 07/11] lib: vsprintf: enable '%pbl' format specifier lukas.funke-oss
2024-01-18 20:22   ` Tom Rini [this message]
2024-01-23 14:48     ` Lukas Funke
2024-01-24  1:32       ` Tom Rini
2024-01-10  9:10 ` [PATCH v3 08/11] setexpr: rename 'get_arg()' to 'setexpr_get_arg()' lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 09/11] setexpr: Promote 'setexpr_get_arg()' to a public function lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 10/11] setexptr: Extend setexpr_get_arg() to handle pointer to memory lukas.funke-oss
2024-01-10  9:10 ` [PATCH v3 11/11] cmd: printf: forward '%p' format string specifier lukas.funke-oss

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=20240118202243.GF12635@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=bmeng.cn@gmail.com \
    --cc=lukas.funke-oss@weidmueller.com \
    --cc=lukas.funke@weidmueller.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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