From: Raag Jadav <raag.jadav@intel.com>
To: mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, rafael@kernel.org,
lenb@kernel.org, robert.moore@intel.com, ardb@kernel.org,
will@kernel.org, mark.rutland@arm.com
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
acpica-devel@lists.linuxfoundation.org,
linux-efi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
mallikarjunappa.sangannavar@intel.com, bala.senthil@intel.com,
Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v2 0/6] Support _UID matching for integer types
Date: Tue, 21 Nov 2023 16:08:23 +0530 [thread overview]
Message-ID: <20231121103829.10027-1-raag.jadav@intel.com> (raw)
This series updates the standard ACPI helpers to support _UID matching
for both integer and string types, and uses them in a couple of places.
Changes since v1:
- Fix build errors
Raag Jadav (6):
compiler.h: Introduce helpers for identifying array and pointer types
ACPI: bus: update acpi_dev_uid_match() to support multiple types
ACPI: bus: update acpi_dev_hid_uid_match() to support multiple types
ACPI: LPSS: use acpi_dev_uid_match() for matching _UID
efi: dev-path-parser: use acpi_dev_uid_match() for matching _UID
perf: arm_cspmu: drop redundant acpi_dev_uid_to_integer()
drivers/acpi/acpi_lpss.c | 16 ++-----
drivers/acpi/utils.c | 48 ---------------------
drivers/firmware/efi/dev-path-parser.c | 7 +--
drivers/perf/arm_cspmu/arm_cspmu.c | 4 +-
include/acpi/acpi_bus.h | 59 +++++++++++++++++++++++++-
include/linux/acpi.h | 15 ++-----
include/linux/compiler.h | 5 +++
7 files changed, 73 insertions(+), 81 deletions(-)
base-commit: f437a8d1debff5412e36a1c9454adee193b31950
--
2.17.1
next reply other threads:[~2023-11-21 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 10:38 Raag Jadav [this message]
2023-11-21 10:38 ` [PATCH v2 1/6] compiler.h: Introduce helpers for identifying array and pointer types Raag Jadav
2023-11-21 10:38 ` [PATCH v2 2/6] ACPI: bus: update acpi_dev_uid_match() to support multiple types Raag Jadav
2023-11-21 16:50 ` Mika Westerberg
2023-11-21 19:25 ` Rafael J. Wysocki
2023-11-22 4:58 ` Raag Jadav
2023-11-22 11:55 ` Rafael J. Wysocki
2023-11-22 10:12 ` Andy Shevchenko
2023-11-21 10:38 ` [PATCH v2 3/6] ACPI: bus: update acpi_dev_hid_uid_match() " Raag Jadav
2023-11-21 16:52 ` Mika Westerberg
2023-11-21 10:38 ` [PATCH v2 4/6] ACPI: LPSS: use acpi_dev_uid_match() for matching _UID Raag Jadav
2023-11-21 16:52 ` Mika Westerberg
2023-11-21 10:38 ` [PATCH v2 5/6] efi: dev-path-parser: " Raag Jadav
2023-11-21 16:19 ` Ard Biesheuvel
2023-11-21 10:38 ` [PATCH v2 6/6] perf: arm_cspmu: drop redundant acpi_dev_uid_to_integer() Raag Jadav
2023-11-21 15:59 ` Will Deacon
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=20231121103829.10027-1-raag.jadav@intel.com \
--to=raag.jadav@intel.com \
--cc=acpica-devel@lists.linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ardb@kernel.org \
--cc=bala.senthil@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=will@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).