From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH v7 0/3] thermal: intel: Use generic trip points in 2 drivers
Date: Mon, 23 Jan 2023 19:45:30 +0100 [thread overview]
Message-ID: <2882611.e9J7NaK4W3@kreacher> (raw)
In-Reply-To: <5916342.lOV4Wx5bFT@kreacher>
On Monday, January 23, 2023 7:36:52 PM CET Rafael J. Wysocki wrote:
> Hi All,
>
> This is a new version of the series from Daniel posted as:
>
> https://lore.kernel.org/linux-pm/20230120231530.2368330-1-daniel.lezcano@linaro.org/
>
> The first patch has been reworked (see https://lore.kernel.org/linux-pm/5911499.lOV4Wx5bFT@kreacher/)
> and the other two have been rebased on top of it.
>
> I have retained the R-by tags from Rui, because the changes in patches [2-3/3] are
> not essential, but I think that this new set needs to be tested again.
>
> Srinivas, can you test it please?
Something's wrong, sorry.
I get some invalid trip temperatures with this set.
next prev parent reply other threads:[~2023-01-23 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 18:36 [PATCH v7 0/3] thermal: intel: Use generic trip points in 2 drivers Rafael J. Wysocki
2023-01-23 18:38 ` [PATCH v7 1/3] thermal: ACPI: Add ACPI trip point routines Rafael J. Wysocki
2023-01-23 18:40 ` [PATCH v7 2/3] thermal: intel: intel_pch: Use generic trip points Rafael J. Wysocki
2023-01-23 18:41 ` [PATCH v7 3/3] thermal: intel: int340x: " Rafael J. Wysocki
2023-01-24 20:43 ` Rafael J. Wysocki
2023-01-25 11:42 ` Rafael J. Wysocki
2023-01-23 18:45 ` Rafael J. Wysocki [this message]
2023-01-23 18:52 ` [PATCH v7 0/3] thermal: intel: Use generic trip points in 2 drivers Rafael J. Wysocki
2023-01-23 19:26 ` srinivas pandruvada
2023-01-23 19:54 ` Rafael J. Wysocki
2023-01-23 21:35 ` srinivas pandruvada
2023-01-24 14:52 ` 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=2882611.e9J7NaK4W3@kreacher \
--to=rjw@rjwysocki.net \
--cc=daniel.lezcano@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.