From patchwork Fri Jan 20 08:19:33 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Johan Hovold X-Patchwork-Id: 645233 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id ED519C25B4E for ; Fri, 20 Jan 2023 08:19:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229613AbjATITz (ORCPT ); Fri, 20 Jan 2023 03:19:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44734 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229529AbjATITy (ORCPT ); Fri, 20 Jan 2023 03:19:54 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6677778ABD; Fri, 20 Jan 2023 00:19:53 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 0346D61E58; Fri, 20 Jan 2023 08:19:53 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 653D1C433D2; Fri, 20 Jan 2023 08:19:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1674202792; bh=wqlS1SJUUlepuHMf3N2ubc3zP0Vjh0qA869+ERCCBto=; h=From:To:Cc:Subject:Date:From; b=IaaPCKvezrZDaVvtC8oyYhxbjTop/0pLYqePgwAYDu5PnJFDjcbnSHNXfjIyqFG5c dWac5Sx1xfrFv9UOHTgsq0ytxNJGkaKPcuDcKWB8HusEG+65WTrx2bgjBBKf9rJvG8 neKyTbyCnBUxUmiz8Pgn3IQdluAhkEejWe+QVr+0/xgaMsM16YclUMdmQWNBxTC/F9 9v0pGaZZfAnPl1z8+zDXmZZo6M39AKDgSwDMsyrAP1WYMwuGEfSt6gi1gyUgNytey6 7mdSpW1daq+q+O7g/tcoaJ48crkUYy+Belvp/S4u2vjoae9rzvXcWFzQ5uNLvR3ONw uNFQEQP1gwTSg== Received: from johan by xi.lan with local (Exim 4.94.2) (envelope-from ) id 1pImdJ-0007bc-QM; Fri, 20 Jan 2023 09:20:22 +0100 From: Johan Hovold To: Ard Biesheuvel Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, Johan Hovold Subject: [PATCH] efi: drop obsolete efivars sysfs documentation Date: Fri, 20 Jan 2023 09:19:33 +0100 Message-Id: <20230120081933.29142-1-johan+linaro@kernel.org> X-Mailer: git-send-email 2.38.2 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-efi@vger.kernel.org The efivars sysfs interface was removed by commit 0f5b2c69a4cb ("efi: vars: Remove deprecated 'efivars' sysfs interface"). Remove also the corresponding sysfs ABI documentation. Signed-off-by: Johan Hovold --- .../ABI/stable/sysfs-firmware-efi-vars | 79 ------------------- 1 file changed, 79 deletions(-) delete mode 100644 Documentation/ABI/stable/sysfs-firmware-efi-vars diff --git a/Documentation/ABI/stable/sysfs-firmware-efi-vars b/Documentation/ABI/stable/sysfs-firmware-efi-vars deleted file mode 100644 index 46ccd233e359..000000000000 --- a/Documentation/ABI/stable/sysfs-firmware-efi-vars +++ /dev/null @@ -1,79 +0,0 @@ -What: /sys/firmware/efi/vars -Date: April 2004 -Contact: Matt Domsch -Description: - This directory exposes interfaces for interactive with - EFI variables. For more information on EFI variables, - see 'Variable Services' in the UEFI specification - (section 7.2 in specification version 2.3 Errata D). - - In summary, EFI variables are named, and are classified - into separate namespaces through the use of a vendor - GUID. They also have an arbitrary binary value - associated with them. - - The efivars module enumerates these variables and - creates a separate directory for each one found. Each - directory has a name of the form "-" - and contains the following files: - - =============== ======================================== - attributes: A read-only text file enumerating the - EFI variable flags. Potential values - include: - - EFI_VARIABLE_NON_VOLATILE - EFI_VARIABLE_BOOTSERVICE_ACCESS - EFI_VARIABLE_RUNTIME_ACCESS - EFI_VARIABLE_HARDWARE_ERROR_RECORD - EFI_VARIABLE_AUTHENTICATED_WRITE_ACCESS - - See the EFI documentation for an - explanation of each of these variables. - - data: A read-only binary file that can be read - to attain the value of the EFI variable - - guid: The vendor GUID of the variable. This - should always match the GUID in the - variable's name. - - raw_var: A binary file that can be read to obtain - a structure that contains everything - there is to know about the variable. - For structure definition see "struct - efi_variable" in the kernel sources. - - This file can also be written to in - order to update the value of a variable. - For this to work however, all fields of - the "struct efi_variable" passed must - match byte for byte with the structure - read out of the file, save for the value - portion. - - **Note** the efi_variable structure - read/written with this file contains a - 'long' type that may change widths - depending on your underlying - architecture. - - size: As ASCII representation of the size of - the variable's value. - =============== ======================================== - - - In addition, two other magic binary files are provided - in the top-level directory and are used for adding and - removing variables: - - =============== ======================================== - new_var: Takes a "struct efi_variable" and - instructs the EFI firmware to create a - new variable. - - del_var: Takes a "struct efi_variable" and - instructs the EFI firmware to remove any - variable that has a matching vendor GUID - and variable key name. - =============== ========================================