From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 1/5] efi: retire efi_bool_t
Date: Mon, 10 Oct 2022 08:08:38 +0200 [thread overview]
Message-ID: <20221010060842.2083550-1-a.fatoum@pengutronix.de> (raw)
GCC defaults to a one-byte bool on all its platform, except for IBM RS/6000,
which will most likely never support. Thus just drop the efi_bool type
we only use at a single place and use bool directly.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
include/efi.h | 1 -
include/efi/efi-stdio.h | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/efi.h b/include/efi.h
index a1b22f2d8f88..691e3d5493fc 100644
--- a/include/efi.h
+++ b/include/efi.h
@@ -62,7 +62,6 @@ struct efi_device_path;
#define EFI_ERROR(a) (((signed long) a) < 0)
typedef unsigned long efi_status_t;
-typedef u8 efi_bool_t;
typedef u16 efi_char16_t; /* UNICODE character */
typedef u64 efi_physical_addr_t;
typedef void *efi_handle_t;
diff --git a/include/efi/efi-stdio.h b/include/efi/efi-stdio.h
index 66fb0afc36b3..e8af244bfcf6 100644
--- a/include/efi/efi-stdio.h
+++ b/include/efi/efi-stdio.h
@@ -8,7 +8,7 @@ struct efi_simple_text_input_ex_protocol;
typedef efi_status_t (EFIAPI *efi_input_reset_ex)(
struct efi_simple_text_input_ex_protocol *this,
- efi_bool_t extended_verification
+ bool extended_verification
);
struct efi_key_state {
--
2.30.2
next reply other threads:[~2022-10-10 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 6:08 Ahmad Fatoum [this message]
2022-10-10 6:08 ` [PATCH 2/5] efi: capitalize enumeration constants Ahmad Fatoum
2022-10-10 6:08 ` [PATCH 3/5] hw_random: add EFI RNG driver Ahmad Fatoum
2022-10-10 6:08 ` [PATCH 4/5] efi: implement and use for_each_efi_config_table Ahmad Fatoum
2022-10-10 6:08 ` [PATCH 5/5] efi: add device tree configuration table support Ahmad Fatoum
2022-10-13 6:33 ` [PATCH 1/5] efi: retire efi_bool_t Sascha Hauer
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=20221010060842.2083550-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--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