From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Daniel Ferguson <danielf@os.amperecomputing.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, "James Morse" <james.morse@arm.com>,
Tony Luck <tony.luck@intel.com>, "Borislav Petkov" <bp@alien8.de>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, <linux-efi@vger.kernel.org>,
<linux-edac@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>
Subject: Re: [PATCH v4 3/5] efi/cper: Add a new helper function to print bitmasks
Date: Fri, 8 Aug 2025 16:23:22 +0100 [thread overview]
Message-ID: <20250808162322.00002485@huawei.com> (raw)
In-Reply-To: <20250805-mauro_v3-v6-16-rev2-v4-3-ea538759841c@os.amperecomputing.com>
On Tue, 05 Aug 2025 11:35:40 -0700
Daniel Ferguson <danielf@os.amperecomputing.com> wrote:
> From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
>
> Add a helper function to print a string with names associated
> to each bit field.
>
> A typical example is:
>
> const char * const bits[] = {
> "bit 3 name",
> "bit 4 name",
> "bit 5 name",
> };
> char str[120];
> unsigned int bitmask = BIT(3) | BIT(5);
>
> #define MASK GENMASK(5,3)
>
> cper_bits_to_str(str, sizeof(str), FIELD_GET(MASK, bitmask),
> bits, ARRAY_SIZE(bits));
>
> The above code fills string "str" with "bit 3 name|bit 5 name".
>
> Reviewed-by; Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
oops. That was probably my mess up. Please fix that ; to : and
put it in the right place.
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> Acked-by: Borislav Petkov (AMD) <bp@alien8.de>
next prev parent reply other threads:[~2025-08-08 15:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 18:35 [PATCH v4 0/5] Fix issues with ARM Processor CPER records Daniel Ferguson
2025-08-05 18:35 ` [PATCH v4 1/5] RAS: Report all ARM processor CPER information to userspace Daniel Ferguson
2025-08-08 15:22 ` Jonathan Cameron
2025-08-09 15:55 ` Mauro Carvalho Chehab
2025-08-11 10:52 ` Jonathan Cameron
2025-08-11 22:37 ` Daniel Ferguson
2025-08-12 14:05 ` Jonathan Cameron
2025-08-05 18:35 ` [PATCH v4 2/5] efi/cper: Adjust infopfx size to accept an extra space Daniel Ferguson
2025-08-05 18:35 ` [PATCH v4 3/5] efi/cper: Add a new helper function to print bitmasks Daniel Ferguson
2025-08-08 15:23 ` Jonathan Cameron [this message]
2025-08-05 18:35 ` [PATCH v4 4/5] efi/cper: align ARM CPER type with UEFI 2.9A/2.10 specs Daniel Ferguson
2025-08-05 18:35 ` [PATCH v4 5/5] docs: efi: add CPER functions to driver-api Daniel Ferguson
2025-08-05 18:39 ` [PATCH v4 0/5] Fix issues with ARM Processor CPER records Daniel Ferguson
2025-08-08 15:01 ` Jonathan Cameron
2025-08-08 19:03 ` Daniel Ferguson
2025-08-09 15:49 ` Mauro Carvalho Chehab
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=20250808162322.00002485@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=danielf@os.amperecomputing.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
/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