The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: [PATCH v2 0/5] ACPI: property: Two fixes, more documentation and a cleanup
Date: Mon, 15 Sep 2025 20:20:03 +0200	[thread overview]
Message-ID: <5922318.DvuYhMxLoT@rafael.j.wysocki> (raw)

Hi All,

This is an update of

https://lore.kernel.org/linux-acpi/5046661.31r3eYUQgx@rafael.j.wysocki/

A user report regarding "ACPI: \: Can't tag data node" error messages in dmesg
made me look at the ACPI property code and I've found a couple of issues in
it.

Also, it took me some time to figure out why the code was doing what it was
doing, so I decided to add some comments explaining it.

Finally, there's always something that can be cleaned up in every piece of
kernel code.

Hence, this series.

Please refer to the patch changelogs for details.

Thanks!




             reply	other threads:[~2025-09-15 18:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 18:20 Rafael J. Wysocki [this message]
2025-09-15 18:21 ` [PATCH v2 1/5] ACPI: property: Fix buffer properties extraction for subnodes Rafael J. Wysocki
2025-09-15 18:23 ` [PATCH v2 2/5] ACPI: property: Disregard references in data-only subnode lists Rafael J. Wysocki
2025-09-15 18:25 ` [PATCH v2 3/5] ACPI: property: Add code comments explaining what is going on Rafael J. Wysocki
2025-09-15 18:28 ` [PATCH v2 4/5] ACPI: property: Do not pass NULL handles to acpi_attach_data() Rafael J. Wysocki
2025-09-15 18:29 ` [PATCH v2 5/5] ACPI: property: Adjust failure handling in acpi_nondev_subnode_extract() Rafael J. Wysocki
2025-09-16 14:09 ` [PATCH v2 0/5] ACPI: property: Two fixes, more documentation and a cleanup Sakari Ailus
2025-09-16 14:10   ` 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=5922318.DvuYhMxLoT@rafael.j.wysocki \
    --to=rafael@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=sakari.ailus@linux.intel.com \
    /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