From: David Arcari <darcari@redhat.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, dedekind1@gmail.com
Cc: linux-pm@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Len Brown <lenb@kernel.org>, Prarit Bhargava <prarit@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] intel_idle: introduce 'use_acpi_cst' module parameter
Date: Wed, 5 Feb 2025 07:09:21 -0500 [thread overview]
Message-ID: <e2eabe42-45b8-4930-af55-857f6e8a4317@redhat.com> (raw)
In-Reply-To: <CAJZ5v0gKsqrruwSBQLk_1cC8MMRyznzE-FbsqDyzs7xFMgZoQQ@mail.gmail.com>
On 2/4/25 12:33 PM, Rafael J. Wysocki wrote:
> On Tue, Feb 4, 2025 at 5:30 PM Artem Bityutskiy <dedekind1@gmail.com> wrote:
>>
>> On Tue, 2025-02-04 at 16:21 +0100, Rafael J. Wysocki wrote:
>>> But it could be something like "prefer_acpi" as far as I'm concerned.
>>
>> When I see "prefer_acpi", my intuition tells that it is just a preference:
>> "prefer ACPI, but may be native too". But I understood that the patch is about
>> "only ACPI and never native".
>>
>> The reasons I suggested "no_native":
>> * Sort of consistent with "no_acpi"
>> * Suggests that native won't work.
>
> "no_native" would be fine by me too.
>
I will send out a v2 using 'no_native' for the new parameter.
-DA
next prev parent reply other threads:[~2025-02-05 12:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 14:11 [PATCH] intel_idle: introduce 'use_acpi_cst' module parameter David Arcari
2025-02-04 12:23 ` Artem Bityutskiy
2025-02-04 12:52 ` David Arcari
2025-02-04 13:04 ` Prarit Bhargava
2025-02-04 15:21 ` Rafael J. Wysocki
2025-02-04 16:30 ` Artem Bityutskiy
2025-02-04 17:33 ` Rafael J. Wysocki
2025-02-05 12:09 ` David Arcari [this message]
2025-02-04 16:26 ` Artem Bityutskiy
2025-02-06 16:40 ` [PATCH v2] intel_idle: introduce 'no_native' " David Arcari
2025-02-07 15:55 ` Artem Bityutskiy
2025-02-07 17:13 ` David Arcari
2025-02-08 10:37 ` Artem Bityutskiy
2025-02-08 19:56 ` David Arcari
2025-02-09 9:08 ` Artem Bityutskiy
2025-02-11 13:27 ` [PATCH v3] " David Arcari
2025-02-12 7:04 ` Artem Bityutskiy
2025-02-12 10:09 ` kernel test robot
2025-02-12 11:32 ` Artem Bityutskiy
2025-02-12 12:41 ` David Arcari
2025-02-12 12:46 ` Artem Bityutskiy
2025-02-12 12:53 ` David Arcari
2025-02-12 12:49 ` Artem Bityutskiy
2025-02-13 11:49 ` kernel test robot
2025-02-13 16:07 ` [PATCH v4] " David Arcari
2025-02-18 19:57 ` Rafael J. Wysocki
2025-02-20 12:50 ` Artem Bityutskiy
2025-02-19 21:27 ` Rafael J. Wysocki
2025-02-20 12:21 ` David Arcari
2025-02-20 12:23 ` Rafael J. Wysocki
2025-02-20 15:11 ` [PATCH v5] " David Arcari
2025-02-20 20:02 ` 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=e2eabe42-45b8-4930-af55-857f6e8a4317@redhat.com \
--to=darcari@redhat.com \
--cc=corbet@lwn.net \
--cc=dedekind1@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=prarit@redhat.com \
--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