linux-kernel - Re: [PATCH v3 1/3] ACPI : introduce macros for using the ACPI specification version

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2553932.NLQ9D78ybW@vostro.rjw.lan>
Date:	Fri, 03 Jul 2015 02:21:02 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Al Stone <al.stone@...aro.org>
Cc:	linux-acpi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	lenb@...nel.org, catalin.marinas@....com, will.deacon@....com,
	tglx@...utronix.de, jason@...edaemon.net,
	linux-kernel@...r.kernel.org, linaro-acpi@...ts.linaro.org,
	linaro-kernel@...ts.linaro.org, patches@...aro.org
Subject: Re: [PATCH v3 1/3] ACPI : introduce macros for using the ACPI specification version

On Thursday, July 02, 2015 05:48:34 PM Al Stone wrote:
> Add the __ACPI_FADT_SPEC_VERSION() helper macro to build a proper version
> number from a major and minor revision number.  Add also macros that use
> the helper to construct the current version from the values in the FADT
> (i.e., ACPI_FADT_SPEC_VERSION) and both the 5.1 and 6.0 versions.
> 
> These macros are added in order to simplify retrieving and comparing ACPI
> specification version numbers, since this is becoming a more frequent need.
> In particular, there are some architectures that require at least a certain
> version of the spec, and there are differences in some structure sizes that
> have changed with recent versions but can only be tracked by spec version
> number.
> 
> Fixes: aeb823bbacc2 (ACPICA: ACPI 6.0: Add changes for FADT table.)
> Signed-off-by: Al Stone <al.stone@...aro.org>
> ---
>  include/linux/acpi.h | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
> index c471dfc..0e525e8 100644
> --- a/include/linux/acpi.h
> +++ b/include/linux/acpi.h
> @@ -48,6 +48,16 @@
>  #include <acpi/acpi_io.h>
>  #include <asm/acpi.h>
>  
> +#define __ACPI_FADT_SPEC_VERSION(major, minor) \
> +	((unsigned int)major << 8 | (unsigned int)minor)
> +
> +#define ACPI_FADT_SPEC_VERSION	\
> +	__ACPI_FADT_SPEC_VERSION(acpi_gbl_FADT.header.revision, \
> +				 acpi_gbl_FADT.minor_revision)
> +
> +#define ACPI_FADT_SPEC_VERSION_51 __ACPI_FADT_SPEC_VERSION(5, 1)
> +#define ACPI_FADT_SPEC_VERSION_60 __ACPI_FADT_SPEC_VERSION(6, 0)

I'd add underscores here, eg. ACPI_FADT_SPEC_VERSION_6_0

And what if there is 5.2 or even 5.3?

> +
>  static inline acpi_handle acpi_device_handle(struct acpi_device *adev)
>  {
>  	return adev ? adev->handle : NULL;
> 

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/