public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 0/2] efi: efivars: drop kobject from efivars_register()
Date: Tue, 17 Jan 2023 13:43:08 +0100	[thread overview]
Message-ID: <20230117124310.16594-1-johan+linaro@kernel.org> (raw)

Since the removal of the deprecated efivars sysfs interface there are
no users of the efivars kobject, which can be removed.

Included is also a related patch changing the return type of
efivar_supports_writes() to match the new efivar_is_available()
function.

Note that I intend to use efivar_is_available() in a driver with
optional EFI support (hence the dummy implementation) and the removal of
the kobject will simplify the upcoming Qualcomm UEFI Secure Application
driver somewhat too.

Johan


Johan Hovold (2):
  efi: efivars: drop kobject from efivars_register()
  efi: efivars: make efivar_supports_writes() return bool

 drivers/firmware/efi/efi.c     |  2 +-
 drivers/firmware/efi/vars.c    | 21 +++++++--------------
 drivers/firmware/google/gsmi.c |  2 +-
 fs/efivarfs/super.c            |  2 +-
 include/linux/efi.h            | 13 ++++++++-----
 5 files changed, 18 insertions(+), 22 deletions(-)

-- 
2.38.2


             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 Johan Hovold [this message]
2023-01-17 12:43 ` [PATCH 1/2] efi: efivars: drop kobject from efivars_register() Johan Hovold
2023-01-17 12:43 ` [PATCH 2/2] efi: efivars: make efivar_supports_writes() return bool Johan Hovold
2023-01-17 16:11 ` [PATCH 0/2] efi: efivars: drop kobject from efivars_register() 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-1-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