public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH v1 0/4] ACPI: utils: Improvements related to struct acpi_handle_list
Date: Fri, 08 Dec 2023 21:03:15 +0100	[thread overview]
Message-ID: <6008018.lOV4Wx5bFT@kreacher> (raw)

Hi All,

This patch series modifies some code related to struct acpi_handle_list.

The first two patches update acpi_evaluate_reference(), which is the only
place where struct acpi_handle_list objects are created, and its callers
to make the code easier to follow, reduce code duplication and get rid of
some useless code and local variables.

The other two patches are a minor modification of a helper function
comparing the contents of two struct acpi_handle_list objects and a white
space fix for the struct acpi_handle_list definition.

The patches in this series are not expected to change the observable behavior
of the kernel.

The series is based on linux-next from today.

Thanks!




             reply	other threads:[~2023-12-08 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 20:03 Rafael J. Wysocki [this message]
2023-12-08 20:05 ` [PATCH v1 1/4] ACPI: utils: Rearrange in acpi_evaluate_reference() Rafael J. Wysocki
2023-12-08 20:06 ` [PATCH v1 2/4] ACPI: utils: Return bool from acpi_evaluate_reference() Rafael J. Wysocki
2023-12-08 20:06 ` [PATCH v1 3/4] ACPI: utils: Refine acpi_handle_list_equal() slightly Rafael J. Wysocki
2023-12-08 20:07 ` [PATCH v1 4/4] ACPI: utils: Fix white space in struct acpi_handle_list definition 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=6008018.lOV4Wx5bFT@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@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