From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: [PATCH 0/3] ACPI property cleanups
Date: Wed, 1 Oct 2025 13:43:17 +0300 [thread overview]
Message-ID: <20251001104320.1272752-1-sakari.ailus@linux.intel.com> (raw)
Hello everyone,
This is a small set of ACPI property cleanups.
The previous set including with the tree-wide changes can be found here
<URL:https://lore.kernel.org/linux-acpi/CAJZ5v0gQ9vnT+Z8zryEausp-2xX7HocoBgwmiptxg7BGiU9C8g@mail.gmail.com/T/#t>.
No functional change intended.
since tree-wide set v2
<20250924074602.266292-1-sakari.ailus@linux.intel.com>, WRT. this patch:
- Don't use kernel-doc functions to document static functions in .c files.
- Use more robust algorithm for enumerating sub-nodes (thanks to Laurent).
since v1 <20250916160129.3955410-1-sakari.ailus@linux.intel.com> (entire
tree-wide set):
- Move patch "ACPI: property: Make acpi_get_next_subnode() static" as
first.
- Add missing parentheses and kernel-doc Return: section in
acpi_get_next_present_subnode() documentation and move the Return
section: of fwnode_graph_get_endpoint_by_id() to the end of the
documentation section (new patch for the latter).
- Use device_get_next_child_node() instead of fwnode_get_next_child_node()
in flash LED driver drivers.
- Rework iterating port nodes in acpi_graph_get_next_endpoint() as
suggested by Andy (new patch).
Sakari Ailus (3):
ACPI: property: Make acpi_get_next_subnode() static
ACPI: property: Use ACPI functions in acpi_graph_get_next_endpoint()
only
ACPI: property: Rework acpi_graph_get_next_endpoint()
drivers/acpi/property.c | 26 +++++++++++++++-----------
include/linux/acpi.h | 10 ----------
2 files changed, 15 insertions(+), 21 deletions(-)
--
2.47.3
next reply other threads:[~2025-10-01 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 10:43 Sakari Ailus [this message]
2025-10-01 10:43 ` [PATCH 1/3] ACPI: property: Make acpi_get_next_subnode() static Sakari Ailus
2025-10-01 10:43 ` [PATCH 2/3] ACPI: property: Use ACPI functions in acpi_graph_get_next_endpoint() only Sakari Ailus
2025-10-01 10:43 ` [PATCH 3/3] ACPI: property: Rework acpi_graph_get_next_endpoint() Sakari Ailus
2025-10-01 12:20 ` Laurent Pinchart
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=20251001104320.1272752-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®