ACPICA version 20201113
Subsystems (2)
cover ACPICA version 20201113
This patch series contains the linux-ized release of ACPICA version 20201113. For Linux, the most notable change is a fix in a memory leak that occurs when evaluating _CID as well as handling orphan _REG methods for GPIO OperationRegions.
Bob Moore (2):
ACPICA: Add 5 new UUIDs to the known UUID table
ACPICA: Update version to 20201113
Colin Ian King (1):
ACPICA: Remove extreaneous "the" in comments
Erik Kaneda (2):
ACPICA: Add function trace macros to improve debugging
ACPICA: Interpreter: fix memory leak by using use existing buffer
Hans de Goede (1):
ACPICA: Also handle "orphan" _REG methods for GPIO OpRegions
drivers/acpi/acpica/accommon.h | 2 +- drivers/acpi/acpica/evregion.c | 54 ++++++++++++++++----------------- drivers/acpi/acpica/nspredef.c | 10 +++--- drivers/acpi/acpica/nsprepkg.c | 38 ++++++++++++----------- drivers/acpi/acpica/nsrepair2.c | 39 +++++++++++------------- include/acpi/acpixf.h | 2 +- include/acpi/acuuid.h | 5 +++ 7 files changed, 77 insertions(+), 73 deletions(-)
Signature · 1 line
2.25.1
PATCH 1/6 ACPICA: Add 5 new UUIDs to the known UUID table
From: Bob Moore <[email protected]>
All UUID entries are related to NVDIMM and the NFIT table.
ACPICA commit c114a02798dd07ccc7e51ffa4365bf039a0dd8d5
--- include/acpi/acuuid.h | 5 +++++ 1 file changed, 5 insertions(+)
include/acpi/acuuid.h +5 -0
@@ -39,6 +39,7 @@/* NVDIMM - NFIT table */ +#define UUID_NFIT_DIMM "4309ac30-0d11-11e4-9191-0800200c9a66"#define UUID_VOLATILE_MEMORY "7305944f-fdda-44e3-b16c-3f22d252e5d0"#define UUID_PERSISTENT_MEMORY "66f0d379-b4f3-4074-ac43-0d3318b78cdb"#define UUID_CONTROL_REGION "92f701f6-13b4-405d-910b-299367e8234c"
@@ -47,6 +48,10 @@#define UUID_VOLATILE_VIRTUAL_CD "3d5abd30-4175-87ce-6d64-d2ade523c4bb"#define UUID_PERSISTENT_VIRTUAL_DISK "5cea02c9-4d07-69d3-269f-4496fbe096f9"#define UUID_PERSISTENT_VIRTUAL_CD "08018188-42cd-bb48-100f-5387d53ded3d" +#define UUID_NFIT_DIMM_N_MSFT "1ee68b36-d4bd-4a1a-9a16-4f8e53d46e05" +#define UUID_NFIT_DIMM_N_HPE1 "9002c334-acf3-4c0e-9642-a235f0d53bc6" +#define UUID_NFIT_DIMM_N_HPE2 "5008664b-b758-41a0-a03c-27c2f2d04f7e" +#define UUID_NFIT_DIMM_N_HYPERV "5746c5f2-a9a2-4264-ad0e-e4ddc9e09e80"/* Processor Properties (ACPI 6.2) */
Signature · 1 line
2.25.1
PATCH 2/6 ACPICA: Remove extreaneous "the" in comments
In reply to Erik KanedaFrom: Colin Ian King <[email protected]>
ACPICA commit f6eae3961bf39ad8beda70c001d1815780600e39
There are several ocurrances of "the the", remove the extraneous "the".
--- drivers/acpi/acpica/accommon.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/acpi/acpica/accommon.h +1 -1
@@ -13,7 +13,7 @@/* * Common set of includes for all ACPICA source files. * We put them here because we don't want to duplicate them -* in the the source code again and again. +* in the source code again and again. * * Note: The order of these include files is important. */
Signature · 1 line
2.25.1
PATCH 3/6 ACPICA: Also handle "orphan" _REG methods for GPIO OpRegions
In reply to Erik KanedaFrom: Hans de Goede <[email protected]>
ACPICA commit b9dc31e2fc67cf196fab5253a9a673bee68b2ef5
Before this commit acpi_ev_execute_reg_methods() had special handling to handle "orphan" (no matching op_region declared) _REG methods for EC nodes.
On Intel Cherry Trail devices there are 2 possible ACPI op_regions for accessing GPIOs. The standard general_purpose_io op_region and the Cherry Trail specific user_defined 0x9X op_regions.
Having 2 different types of op_regions leads to potential issues with checks for op_region availability, or in other words checks if _REG has been called for the op_region which the ACPI code wants to use.
Except for the "orphan" EC handling, ACPICA core does not call _REG on an ACPI node which does not define an op_region matching the type being registered; and the reference design DSDT, from which most Cherry Trail DSDTs are derived, does not define general_purpose_io, nor user_defined(0x93) op_regions for the GPO2 (UID 3) device, because no pins were assigned ACPI controlled functions in the reference design.
Together this leads to the perfect storm, at least on the Cherry Trail based Medion Akayo E1239T. This design does use a GPO2 pin from its ACPI code and has added the Cherry Trail specific user_defined(0x93) opregion to its GPO2 ACPI node to access this pin.
But it uses a has _REG been called availability check for the standard general_purpose_io op_region. This clearly is a bug in the DSDT, but this does work under Windows. This issue leads to the intel_vbtn driver reporting the device always being in tablet-mode at boot, even if it is in laptop mode. Which in turn causes userspace to ignore touchpad events. So iow this issues causes the touchpad to not work at boot.
This commit fixes this by extending the "orphan" _REG method handling to also apply to GPIO address-space handlers.
Note it seems that Windows always calls "orphan" _REG methods so me may want to consider dropping the space-id check and always do "orphan" _REG method handling.
--- drivers/acpi/acpica/evregion.c | 54 +++++++++++++++++----------------- 1 file changed, 27 insertions(+), 27 deletions(-)
drivers/acpi/acpica/evregion.c +27 -27
@@ -21,7 +21,8 @@ extern u8 acpi_gbl_default_address_spaces[];/* Local prototypes */ static void -acpi_ev_orphan_ec_reg_method (struct acpi_namespace_node *ec_device_node); +acpi_ev_execute_orphan_reg_method (struct acpi_namespace_node *device_node, +acpi_adr_space_type space_id); static acpi_status acpi_ev_reg_run(acpi_handle obj_handle,
@@ -684,10 +685,12 @@ acpi_ev_execute_reg_methods(struct acpi_namespace_node *node,ACPI_NS_WALK_UNLOCK , acpi_ev_reg_run,NULL , &info, NULL); -/* Special case for EC: handle "orphan" _REG methods with no region */ - -if (space_id ==ACPI_ADR_SPACE_EC ) { -acpi_ev_orphan_ec_reg_method (node); +/* +* Special case for EC and GPIO: handle "orphan" _REG methods with +* no region. +*/ +if (space_id ==ACPI_ADR_SPACE_EC || space_id ==ACPI_ADR_SPACE_GPIO ) { +acpi_ev_execute_orphan_reg_method (node, space_id); } ACPI_DEBUG_PRINT_RAW((ACPI_DB_NAMES,
@@ -760,31 +763,28 @@ acpi_ev_reg_run(acpi_handle obj_handle,/******************************************************************************* * -* FUNCTION: acpi_ev_orphan_ec_reg_method +* FUNCTION: acpi_ev_execute_orphan_reg_method * -* PARAMETERS: ec_device_node - Namespace node for an EC device +* PARAMETERS: device_node - Namespace node for an ACPI device +* space_id - The address space ID * * RETURN: None * -* DESCRIPTION: Execute an "orphan" _REG method that appears under the EC +* DESCRIPTION: Execute an "orphan" _REG method that appears under an ACPI * device. This is a _REG method that has no corresponding region -* within the EC device scope. The orphan _REG method appears to -* have been enabled by the description of the ECDT in the ACPI -* specification: "The availability of the region space can be -* detected by providing a _REG method object underneath the -* Embedded Controller device." -* -* To quickly access the EC device, we use the ec_device_node used -* during EC handler installation. Otherwise, we would need to -* perform a time consuming namespace walk, executing _HID -* methods to find the EC device. +* within the device's scope. ACPI tables depending on these +* "orphan" _REG methods have been seen for both EC and GPIO +* Operation Regions. Presumably the Windows ACPI implementation +* always calls the _REG method independent of the presence of +* an actual Operation Region with the correct address space ID. * * MUTEX: Assumes the namespace is locked * ******************************************************************************/ static void -acpi_ev_orphan_ec_reg_method (struct acpi_namespace_node *ec_device_node) +acpi_ev_execute_orphan_reg_method (struct acpi_namespace_node *device_node, +acpi_adr_space_type space_id) {acpi_handle reg_method;struct acpi_namespace_node *next_node;
@@ -792,9 +792,9 @@ acpi_ev_orphan_ec_reg_method(struct acpi_namespace_node *ec_device_node)struct acpi_object_list args;union acpi_object objects[2 ]; -ACPI_FUNCTION_TRACE (ev_orphan_ec_reg_method); +ACPI_FUNCTION_TRACE (ev_execute_orphan_reg_method); -if (!ec_device_node) { +if (!device_node) { return_VOID; }
@@ -804,7 +804,7 @@ acpi_ev_orphan_ec_reg_method(struct acpi_namespace_node *ec_device_node)/* Get a handle to a _REG method immediately under the EC device */ - status =acpi_get_handle (ec_device_node,METHOD_NAME__REG , ®_method); + status =acpi_get_handle (device_node,METHOD_NAME__REG , ®_method);if (ACPI_FAILURE (status)) { goto exit;/* There is no _REG method present */ }
@@ -816,23 +816,23 @@ acpi_ev_orphan_ec_reg_method(struct acpi_namespace_node *ec_device_node)* with other space IDs to be present; but the code below will then * execute the _REG method with the embedded_control space_ID argument. */ - next_node =acpi_ns_get_next_node (ec_device_node,NULL ); + next_node =acpi_ns_get_next_node (device_node,NULL );while (next_node) {if ((next_node->type ==ACPI_TYPE_REGION ) && (next_node->object) && - (next_node->object->region.space_id ==ACPI_ADR_SPACE_EC )) { + (next_node->object->region.space_id == space_id)) { goto exit;/* Do not execute the _REG */ } - next_node =acpi_ns_get_next_node (ec_device_node, next_node); + next_node =acpi_ns_get_next_node (device_node, next_node); } -/* Evaluate the _REG(embedded_control,Connect) method */ +/* Evaluate the _REG(space_id,Connect) method */ args.count =2 ; args.pointer = objects; objects[0 ].type =ACPI_TYPE_INTEGER ; - objects[0 ].integer.value =ACPI_ADR_SPACE_EC ; + objects[0 ].integer.value = space_id; objects[1 ].type =ACPI_TYPE_INTEGER ; objects[1 ].integer.value =ACPI_REG_CONNECT ;
Signature · 1 line
2.25.1
PATCH 4/6 ACPICA: Add function trace macros to improve debugging
In reply to Erik KanedaACPICA commit 87b8dba05b4cf8c111948327023c710e2b6b5a05
The namespace repair mechanism does not have function tracing macros. Add several trace macros to improve debuggability.
--- drivers/acpi/acpica/nspredef.c | 10 +++++---- drivers/acpi/acpica/nsprepkg.c | 38 +++++++++++++++++---------------- drivers/acpi/acpica/nsrepair2.c | 24 ++++++++++++--------- 3 files changed, 40 insertions(+), 32 deletions(-)
drivers/acpi/acpica/nspredef.c +6 -4
@@ -71,11 +71,13 @@ acpi_ns_check_return_value(struct acpi_namespace_node *node,acpi_status status;const union acpi_predefined_info *predefined; +ACPI_FUNCTION_TRACE (ns_check_return_value); +/* If not a predefined name, we cannot validate the return object */ predefined = info->predefined;if (!predefined) { -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }/*
@@ -83,7 +85,7 @@ acpi_ns_check_return_value(struct acpi_namespace_node *node,* validate the return object */ if ((return_status !=AE_OK ) && (return_status !=AE_CTRL_RETURN_VALUE )) { -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }/*
@@ -102,7 +104,7 @@ acpi_ns_check_return_value(struct acpi_namespace_node *node,if (acpi_gbl_disable_auto_repair || (!predefined->info.expected_btypes) || (predefined->info.expected_btypes ==ACPI_RTYPE_ALL )) { -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }/*
@@ -163,7 +165,7 @@ acpi_ns_check_return_value(struct acpi_namespace_node *node, node->flags |=ANOBJ_EVALUATED ; } -return (status); +return_ACPI_STATUS (status); }/*******************************************************************************
drivers/acpi/acpica/nsprepkg.c +20 -18
@@ -59,7 +59,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info,u32 count;u32 i; -ACPI_FUNCTION_NAME (ns_check_package); +ACPI_FUNCTION_TRACE (ns_check_package);/* The package info for this name is in the next table entry */
@@ -88,14 +88,14 @@ acpi_ns_check_package(struct acpi_evaluate_info *info,*/ if (!count) {if (package->ret_info.type ==ACPI_PTYPE1_VAR ) { -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }ACPI_WARN_PREDEFINED ((AE_INFO , info->full_pathname, info->node_flags,"Return Package has no elements (empty)" )); -return (AE_AML_OPERAND_VALUE ); +return_ACPI_STATUS (AE_AML_OPERAND_VALUE ); }/*
@@ -152,7 +152,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info, package->ret_info. object_type1, i);if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); } elements++;
@@ -186,7 +186,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info, object_type[i], i);if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); } }else {/* These are the optional package elements */
@@ -198,7 +198,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info, tail_object_type, i);if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); } }
@@ -214,7 +214,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info,acpi_ns_check_object_type (info, elements,ACPI_RTYPE_INTEGER ,0 );if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); } elements++;
@@ -234,7 +234,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info,acpi_ns_check_object_type (info, elements,ACPI_RTYPE_INTEGER ,0 );if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); }/*
@@ -279,7 +279,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info,acpi_ns_wrap_with_package (info, return_object, return_object_ptr);if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); }/* Update locals to point to the new package (of 1 element) */
@@ -316,7 +316,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info, package->ret_info. object_type1, 0);if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); }/* Validate length of the UUID buffer */
@@ -326,14 +326,14 @@ acpi_ns_check_package(struct acpi_evaluate_info *info, info->full_pathname, info->node_flags, "Invalid length for UUID Buffer")); -return (AE_AML_OPERAND_VALUE ); +return_ACPI_STATUS (AE_AML_OPERAND_VALUE ); } status =acpi_ns_check_object_type (info, elements +1 , package->ret_info. object_type2,0 );if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); } elements +=2 ;
@@ -350,10 +350,10 @@ acpi_ns_check_package(struct acpi_evaluate_info *info,"Invalid internal return type in table entry: %X" , package->ret_info.type)); -return (AE_AML_INTERNAL ); +return_ACPI_STATUS (AE_AML_INTERNAL ); } -return (status); +return_ACPI_STATUS (status); package_too_small:
@@ -363,7 +363,7 @@ acpi_ns_check_package(struct acpi_evaluate_info *info,"Return Package is too small - found %u elements, expected %u" , count, expected_count)); -return (AE_AML_OPERAND_VALUE ); +return_ACPI_STATUS (AE_AML_OPERAND_VALUE ); }/*******************************************************************************
@@ -708,6 +708,8 @@ acpi_ns_check_package_elements(struct acpi_evaluate_info *info,acpi_status status;u32 i; +ACPI_FUNCTION_TRACE (ns_check_package_elements); +/* * Up to two groups of package elements are supported by the data * structure. All elements in each group must be of the same type.
@@ -717,7 +719,7 @@ acpi_ns_check_package_elements(struct acpi_evaluate_info *info, status =acpi_ns_check_object_type (info, this_element, type1, i + start_index);if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); } this_element++;
@@ -728,11 +730,11 @@ acpi_ns_check_package_elements(struct acpi_evaluate_info *info, type2, (i + count1 + start_index));if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); } this_element++; } -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }
drivers/acpi/acpica/nsrepair2.c +14 -10
@@ -155,15 +155,17 @@ acpi_ns_complex_repairs(struct acpi_evaluate_info *info,const struct acpi_repair_info *predefined;acpi_status status; +ACPI_FUNCTION_TRACE (ns_complex_repairs); +/* Check if this name is in the list of repairable names */ predefined =acpi_ns_match_complex_repair (node);if (!predefined) { -return (validate_status); +return_ACPI_STATUS (validate_status); } status = predefined->repair_function (info, return_object_ptr); -return (status); +return_ACPI_STATUS (status); }/******************************************************************************
@@ -344,17 +346,19 @@ acpi_ns_repair_CID(struct acpi_evaluate_info *info,u16 original_ref_count;u32 i; +ACPI_FUNCTION_TRACE (ns_repair_CID); +/* Check for _CID as a simple string */ if (return_object->common.type ==ACPI_TYPE_STRING ) { status =acpi_ns_repair_HID (info, return_object_ptr); -return (status); +return_ACPI_STATUS (status); }/* Exit if not a Package */ if (return_object->common.type !=ACPI_TYPE_PACKAGE ) { -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }/* Examine each element of the _CID package */
@@ -366,7 +370,7 @@ acpi_ns_repair_CID(struct acpi_evaluate_info *info, status =acpi_ns_repair_HID (info, element_ptr);if (ACPI_FAILURE (status)) { -return (status); +return_ACPI_STATUS (status); }if (original_element != *element_ptr) {
@@ -380,7 +384,7 @@ acpi_ns_repair_CID(struct acpi_evaluate_info *info, element_ptr++; } -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }/******************************************************************************
@@ -500,7 +504,7 @@ acpi_ns_repair_HID(struct acpi_evaluate_info *info,/* We only care about string _HID objects (not integers) */ if (return_object->common.type !=ACPI_TYPE_STRING ) { -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }if (return_object->string.length ==0 ) {
@@ -511,14 +515,14 @@ acpi_ns_repair_HID(struct acpi_evaluate_info *info,/* Return AE_OK anyway, let driver handle it */ info->return_flags |=ACPI_OBJECT_REPAIRED ; -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }/* It is simplest to always create a new string object */ new_string =acpi_ut_create_string_object (return_object->string.length);if (!new_string) { -return (AE_NO_MEMORY ); +return_ACPI_STATUS (AE_NO_MEMORY ); }/*
@@ -551,7 +555,7 @@ acpi_ns_repair_HID(struct acpi_evaluate_info *info,acpi_ut_remove_reference (return_object); *return_object_ptr = new_string; -return (AE_OK ); +return_ACPI_STATUS (AE_OK ); }/******************************************************************************
Signature · 1 line
2.25.1
PATCH 5/6 ACPICA: Interpreter: fix memory leak by using existing buffer
In reply to Erik KanedaACPICA commit 52d1da5dcbd79a722b70f02a1a83f04088f51ff6
There was a memory leak that ocurred when a _CID object is defined as a package containing string objects. When _CID is checked for any possible repairs, it calls a helper function to repair _HID (because _CID basically contains multiple _HID entries).
The _HID repair function assumes that string objects are standalone objects that are not contained inside of any packages. The _HID repair function replaces the string object with a brand new object and attempts to delete the old object by decrementing the reference count of the old object. Strings inside of packages have a reference count of 2 so the _HID repair function leaves this object in a dangling state and causes a memory leak.
Instead of allocating a brand new object and removing the old object, use the existing object when repairing the _HID object.
--- drivers/acpi/acpica/nsrepair2.c | 17 ++++------------- 1 file changed, 4 insertions(+), 13 deletions(-)
drivers/acpi/acpica/nsrepair2.c +4 -13
@@ -495,9 +495,8 @@ acpi_ns_repair_HID(struct acpi_evaluate_info *info, union acpi_operand_object **return_object_ptr) {union acpi_operand_object *return_object = *return_object_ptr; -union acpi_operand_object *new_string; -char *source;char *dest; +char *source;ACPI_FUNCTION_NAME (ns_repair_HID);
@@ -518,13 +517,6 @@ acpi_ns_repair_HID(struct acpi_evaluate_info *info,return_ACPI_STATUS (AE_OK ); } -/* It is simplest to always create a new string object */ - - new_string =acpi_ut_create_string_object (return_object->string.length); -if (!new_string) { -return_ACPI_STATUS (AE_NO_MEMORY ); - } -/* * Remove a leading asterisk if present. For some unknown reason, there * are many machines in the field that contains IDs like this.
@@ -534,7 +526,7 @@ acpi_ns_repair_HID(struct acpi_evaluate_info *info, source = return_object->string.pointer;if (*source =='*' ) { source++; - new_string->string.length--; + return_object->string.length--; ACPI_DEBUG_PRINT((ACPI_DB_REPAIR, "%s: Removed invalid leading asterisk\n",
@@ -549,12 +541,11 @@ acpi_ns_repair_HID(struct acpi_evaluate_info *info,* "NNNN####" where N is an uppercase letter or decimal digit, and * # is a hex digit. */ -for (dest = new_string->string.pointer; *source; dest++, source++) { +for (dest = return_object->string.pointer; *source; dest++, source++) { *dest = (char )toupper ((int )*source); } + return_object->string.pointer[return_object->string.length] =0 ; -acpi_ut_remove_reference (return_object); - *return_object_ptr = new_string;return_ACPI_STATUS (AE_OK ); }
Signature · 1 line
2.25.1
PATCH 6/6 ACPICA: Update version to 20201113
In reply to Erik KanedaFrom: Bob Moore <[email protected]>
ACPICA commit 090f0444238bd49f563bf80f4f3a863463dfdf78
Version 20201113.
--- include/acpi/acpixf.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/acpi/acpixf.h +1 -1
@@ -12,7 +12,7 @@/* Current ACPICA subsystem version in YYYYMMDD format */ -#define ACPI_CA_VERSION 0x20200925 +#define ACPI_CA_VERSION 0x20201113#include <acpi/acconfig.h> #include <acpi/actypes.h>
Signature · 1 line
2.25.1
Rafael J. Wysocki
maintainerQuoted 29 lines · Erik Kaneda
This patch series contains the linux-ized release of ACPICA version 20201113. For Linux, the most notable change is a fix in a memory leak that occurs when evaluating
_CIDas well as handling orphan_REGmethods for GPIO OperationRegions.Bob Moore (2):
ACPICA: Add 5 new UUIDs to the known UUID table
ACPICA: Update version to 20201113Colin Ian King (1):
ACPICA: Remove extreaneous "the" in commentsErik Kaneda (2):
ACPICA: Add function trace macros to improve debugging
ACPICA: Interpreter: fix memory leak by using use existing bufferHans de Goede (1):
ACPICA: Also handle "orphan"_REGmethods for GPIO OpRegionsdrivers/acpi/acpica/accommon.h | 2 +- drivers/acpi/acpica/evregion.c | 54 ++++++++++++++++----------------- drivers/acpi/acpica/nspredef.c | 10 +++--- drivers/acpi/acpica/nsprepkg.c | 38 ++++++++++++----------- drivers/acpi/acpica/nsrepair2.c | 39 +++++++++++------------- include/acpi/acpixf.h | 2 +- include/acpi/acuuid.h | 5 +++ 7 files changed, 77 insertions(+), 73 deletions(-)
Quoted 1 line
--
All applied as 5.11-rc material, thanks!