From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Saravana Kannan <saravanak@google.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH v1 0/2] PM: core: Updates related to device link lists
Date: Sat, 6 Sep 2025 14:01:46 +0200 [thread overview]
Message-ID: <2025090641-reveal-swab-6e2b@gregkh> (raw)
In-Reply-To: <6202205.lOV4Wx5bFT@rafael.j.wysocki>
On Tue, Sep 02, 2025 at 03:40:54PM +0200, Rafael J. Wysocki wrote:
> Hi All,
>
> The changes in this series clean up the usage of _rcu list walks for
> walking lists of a device's links to suppliers and consumers.
>
> The first patch changes the _rcu annotation of those list walks to
> the _srcu one which is more appropriate because SRCU is used for
> device link lists protection.
>
> The second patch (which is not expected to make any functional difference)
> adds two macros for walking lists of a device's links to suppliers and
> consumers and updates power management code walking those lists to use
> the new macros for more clarity and protection against possible coding
> mistakes.
>
> Thanks!
>
>
>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2025-09-06 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 13:40 [PATCH v1 0/2] PM: core: Updates related to device link lists Rafael J. Wysocki
2025-09-02 13:43 ` [PATCH v1 1/2] PM: core: Annotate loops walking device links as _srcu Rafael J. Wysocki
2025-09-04 9:23 ` Ulf Hansson
2025-09-02 13:45 ` [PATCH v1 2/2] PM: core: Add two macros for walking device links Rafael J. Wysocki
2025-09-04 9:23 ` Ulf Hansson
2025-09-06 12:01 ` Greg Kroah-Hartman [this message]
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=2025090641-reveal-swab-6e2b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dakr@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=ulf.hansson@linaro.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