[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250530102711.GAaDmH_1O7lc6kuveY@fat_crate.local>
Date: Fri, 30 May 2025 12:27:11 +0200
From: Borislav Petkov <bp@...en8.de>
To: Zaid Alali <zaidal@...amperecomputing.com>
Cc: rafael@...nel.org, lenb@...nel.org, james.morse@....com,
tony.luck@...el.com, robert.moore@...el.com,
Jonathan.Cameron@...wei.com, ira.weiny@...el.com,
Benjamin.Cheatham@....com, dan.j.williams@...el.com, arnd@...db.de,
Avadhut.Naik@....com, u.kleine-koenig@...gutronix.de,
john.allen@....com, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, acpica-devel@...ts.linux.dev
Subject: Re: [PATCH v7 9/9] ACPI: APEI: EINJ: Update the documentation for
EINJv2 support
On Tue, May 06, 2025 at 02:38:13PM -0700, Zaid Alali wrote:
> +- einjv2_component_array
> +
> + The contents of this file are used to set the "Component Array" field
> + of the EINJv2 Extension Structure. The expected format is hex values
> + for component id and syndrome separated by space, and multiple
> + components are separated by new line.
How is this a good design?
Do you guys not see that the other injection files are one value per file?
> + # comp_arr="0x1 0x2 # Fill in the component array
> + >0x1 0x4
> + >0x2 0x4"
> + # echo "$comp_arr" > einjv2_component_array
Oh boy. Srsly?!
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists