linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hanjun.guo@linaro.org (Hanjun Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ACPI : introduce macros for using the ACPI specification version
Date: Fri, 19 Jun 2015 18:49:11 +0800	[thread overview]
Message-ID: <5583F3A7.4020202@linaro.org> (raw)
In-Reply-To: <1434666968-1543-2-git-send-email-al.stone@linaro.org>

On 06/19/2015 06:36 AM, Al Stone wrote:
> Add the ACPI_SPEC_VERSION() macro to build a proper version number from
> a major and minor revision number.  Add also the ACPI_FADT_SPEC_VERSION
> that constructs a proper version number from the entries in the current
> FADT.
>
> 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.
>
> Signed-off-by: Al Stone <al.stone@linaro.org>
> ---
>   include/linux/acpi.h | 5 +++++
>   1 file changed, 5 insertions(+)
>
> diff --git a/include/linux/acpi.h b/include/linux/acpi.h
> index a4acb55..33ed313 100644
> --- a/include/linux/acpi.h
> +++ b/include/linux/acpi.h
> @@ -48,6 +48,11 @@
>   #include <acpi/acpi_io.h>
>   #include <asm/acpi.h>
>
> +#define ACPI_SPEC_VERSION(major, minor)	((major<<8)|minor)

and minor comments for code style

((major<<8)|minor) - > ((major << 8) | minor)

other than that:

Reviewed-by: Hanjun Guo <hanjun.guo@linaro.org>

Thanks
Hanjun

> +#define ACPI_FADT_SPEC_VERSION	\
> +	ACPI_SPEC_VERSION(acpi_gbl_FADT.header.revision, \
> +			  acpi_gbl_FADT.minor_revision)
> +
>   static inline acpi_handle acpi_device_handle(struct acpi_device *adev)
>   {
>   	return adev ? adev->handle : NULL;
>

  reply	other threads:[~2015-06-19 10:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 22:36 [PATCH v2 0/3] Correct for ACPI 5.1->6.0 spec changes in MADT GICC entries Al Stone
2015-06-18 22:36 ` [PATCH v2 1/3] ACPI : introduce macros for using the ACPI specification version Al Stone
2015-06-19 10:49   ` Hanjun Guo [this message]
2015-06-19 20:01     ` Al Stone
2015-06-30 20:12   ` Rafael J. Wysocki
2015-06-30 21:15     ` Al Stone
2015-07-01  2:30       ` Hanjun Guo
2015-06-18 22:36 ` [PATCH v2 2/3] ACPI: add BAD_MADT_GICC_ENTRY() macro Al Stone
2015-06-19 10:49   ` Hanjun Guo
2015-06-19 20:02     ` Al Stone
2015-06-18 22:36 ` [PATCH v2 3/3] ACPI / ARM64 : use the new BAD_MADT_GICC_ENTRY macro Al Stone
2015-06-19  9:46   ` Will Deacon
2015-06-19 20:03     ` Al Stone
2015-06-19 10:52   ` Hanjun Guo
2015-06-19 10:54 ` [PATCH v2 0/3] Correct for ACPI 5.1->6.0 spec changes in MADT GICC entries Hanjun Guo
2015-06-19 20:05   ` Al Stone
2015-06-30 17:07 ` Sudeep Holla
2015-06-30 17:29   ` Al Stone
2015-06-30 18:25     ` Rafael J. Wysocki
2015-06-30 18:35       ` Rafael J. Wysocki
2015-07-01  2:06         ` Hanjun Guo
2015-07-02 18:25           ` Al Stone
2015-06-30 18:39       ` Al Stone
2015-06-30 19:05         ` Rafael J. Wysocki
2015-06-30 19:57           ` Al Stone
2015-06-30 19:45       ` Al Stone
2015-06-30 19:58         ` Rafael J. Wysocki

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=5583F3A7.4020202@linaro.org \
    --to=hanjun.guo@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).