Date: Mon, 03 Feb 2025 17:38:40 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: hackers@freebsd.org Subject: Re: %b with uint64_t? Message-ID: <86bjvjgezz.fsf@ltc.des.dev> In-Reply-To: <86frkvgfn6.fsf@ltc.des.dev> ("Dag-Erling =?utf-8?Q?Sm=C3=B8r?= =?utf-8?Q?grav=22's?= message of "Mon, 03 Feb 2025 17:24:45 %2B0100") References: <157p941p-159p-rn75-2qo9-6762o7sprq40@yvfgf.mnoonqbm.arg> <86frkvgfn6.fsf@ltc.des.dev>
index | next in thread | previous in thread | raw e-mail
Dag-Erling Smørgrav <des@FreeBSD.org> writes: > "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> writes: > > I recently ran into a problem with a uint64_t bitflag to use the %b > > print format in the kernel. > The correct format string to print a uint64_t as binary is %w64b. > [...] Ah, please ignore me, I missed the “kernel” part and thought you were talking about N2630 / N2680. DES -- Dag-Erling Smørgrav - des@FreeBSD.orghelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86bjvjgezz.fsf>