From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] PM: sleep: Restore asynchronous device resume optimization
Date: Wed, 10 Jan 2024 15:05:01 +0100 [thread overview]
Message-ID: <ZZ6kDVD3p4KdR9Cs@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0gp6uETgLNHxDnSd4h_0ois7J2AC7soJJVv18B99GmxcQ@mail.gmail.com>
On Wed, Jan 10, 2024 at 01:33:07PM +0100, Rafael J. Wysocki wrote:
> > I would consider different naming just to make clear this
> > is regarding async call, in_progress looks too generic for me.
>
> OK, what about async_in_progress?
Sure, that better.
Regards
Stanislaw
next prev parent reply other threads:[~2024-01-10 14:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 16:59 [PATCH v1] PM: sleep: Restore asynchronous device resume optimization Rafael J. Wysocki
2024-01-10 10:37 ` Stanislaw Gruszka
2024-01-10 12:33 ` Rafael J. Wysocki
2024-01-10 14:05 ` Stanislaw Gruszka [this message]
2024-01-11 7:58 ` Stanislaw Gruszka
2024-01-11 12:01 ` Rafael J. Wysocki
[not found] ` <CGME20240207103144eucas1p16b601a73ff347d2542f8380b25921491@eucas1p1.samsung.com>
2024-02-07 10:31 ` Marek Szyprowski
2024-02-07 10:38 ` Rafael J. Wysocki
2024-02-07 11:16 ` Marek Szyprowski
2024-02-07 11:25 ` Rafael J. Wysocki
2024-02-07 16:39 ` Tejun Heo
2024-02-07 18:41 ` Rafael J. Wysocki
2024-02-07 18:55 ` Marek Szyprowski
2024-02-07 18:58 ` Tejun Heo
2024-02-07 19:48 ` Tejun Heo
2024-02-07 19:54 ` Rafael J. Wysocki
2024-02-07 21:30 ` Marek Szyprowski
2024-02-07 21:35 ` Tejun Heo
2024-02-08 7:47 ` Marek Szyprowski
2024-02-09 0:20 ` Tejun Heo
2024-02-12 14:57 ` Rafael J. Wysocki
2024-02-07 10:59 ` Rafael J. Wysocki
2024-02-10 14:04 ` Konrad Dybcio
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=ZZ6kDVD3p4KdR9Cs@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).