From: Johan Hovold <johan+linaro@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
Jeremy Kerr <jk@ozlabs.org>,
Maximilian Luz <luzmaximilian@gmail.com>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH 2/2] efi: efivars: make efivar_supports_writes() return bool
Date: Tue, 17 Jan 2023 13:43:10 +0100 [thread overview]
Message-ID: <20230117124310.16594-3-johan+linaro@kernel.org> (raw)
In-Reply-To: <20230117124310.16594-1-johan+linaro@kernel.org>
For consistency with the new efivar_is_available() function, change the
return type of efivar_supports_writes() to bool.
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
---
drivers/firmware/efi/vars.c | 2 +-
include/linux/efi.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/firmware/efi/vars.c b/drivers/firmware/efi/vars.c
index d6b2c4f9a575..aa5ba38f81ff 100644
--- a/drivers/firmware/efi/vars.c
+++ b/drivers/firmware/efi/vars.c
@@ -110,7 +110,7 @@ int efivars_unregister(struct efivars *efivars)
}
EXPORT_SYMBOL_GPL(efivars_unregister);
-int efivar_supports_writes(void)
+bool efivar_supports_writes(void)
{
return __efivars && __efivars->ops->set_variable;
}
diff --git a/include/linux/efi.h b/include/linux/efi.h
index 2124e55c02d6..f6b107da1cbc 100644
--- a/include/linux/efi.h
+++ b/include/linux/efi.h
@@ -1061,7 +1061,7 @@ bool efivar_is_available(void);
static inline bool efivar_is_available(void) { return false; }
#endif
-int efivar_supports_writes(void);
+bool efivar_supports_writes(void);
int efivar_lock(void);
int efivar_trylock(void);
--
2.38.2
next prev parent reply other threads:[~2023-01-17 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 12:43 [PATCH 0/2] efi: efivars: drop kobject from efivars_register() Johan Hovold
2023-01-17 12:43 ` [PATCH 1/2] " Johan Hovold
2023-01-17 12:43 ` Johan Hovold [this message]
2023-01-17 16:11 ` [PATCH 0/2] " Ard Biesheuvel
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=20230117124310.16594-3-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=ardb@kernel.org \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=matthew.garrett@nebula.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