From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Zhang Rui <rui.zhang@intel.com>,
David Box <david.e.box@linux.intel.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Subject: [PATCH v2 0/2] intel_idle: Two new module parameters
Date: Mon, 03 Feb 2020 12:13:41 +0100 [thread overview]
Message-ID: <1921392.EN65KG1giI@kreacher> (raw)
In-Reply-To: <1720216.0Jr2BLnqKp@kreacher>
On Thursday, January 30, 2020 3:44:40 PM CET Rafael J. Wysocki wrote:
> Hi All,
>
> This series adds to module parameters to intel_idle (on top of the material
> already in the mainline since Monday), one to make it use ACPI even if that
> is not enabled for the processor model present in the system and the other
> one to allow passing a list of idle states to disable by default to it.
>
> Details in the patch changelogs.
This is a small update of the original set fixing a build issue in the first
patch and addressing a couple of review comments in the second one.
Thanks,
Rafael
next prev parent reply other threads:[~2020-02-03 11:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 14:44 [PATCH 0/2] intel_idle: Two new module parameters Rafael J. Wysocki
2020-01-30 14:46 ` [PATCH 1/2] intel_idle: Introduce 'use_acpi' module parameter Rafael J. Wysocki
2020-02-02 14:23 ` kbuild test robot
2020-01-30 14:47 ` [PATCH 2/2] intel_idle: Introduce 'states_off' " Rafael J. Wysocki
2020-01-31 11:07 ` David Laight
2020-01-31 11:23 ` Rafael J. Wysocki
2020-01-31 11:24 ` Artem Bityutskiy
2020-01-31 11:54 ` David Laight
2020-01-31 12:03 ` Rafael J. Wysocki
2020-02-03 11:13 ` Rafael J. Wysocki [this message]
2020-02-03 11:15 ` [PATCH v2 1/2] intel_idle: Introduce 'use_acpi' " Rafael J. Wysocki
2020-02-03 11:19 ` [PATCH v2 2/2] intel_idle: Introduce 'states_off' " 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=1921392.EN65KG1giI@kreacher \
--to=rjw@rjwysocki.net \
--cc=artem.bityutskiy@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@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