From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
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 13:35:35 -0800 [thread overview]
Message-ID: <ca878d5a177b68eaf5f698e0afda5c0b1718a53f.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0gK_O-9_tPEVbmBbf+2vxVA2_C5tPGOo_qghyw86pohoA@mail.gmail.com>
On Mon, 2023-01-23 at 20:54 +0100, Rafael J. Wysocki wrote:
> On Mon, Jan 23, 2023 at 8:26 PM srinivas pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> >
> > On Mon, 2023-01-23 at 19:52 +0100, Rafael J. Wysocki wrote:
> > > On Monday, January 23, 2023 7:45:30 PM CET Rafael J. Wysocki
> > > wrote:
> > > > 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.
> > >
> > > Sorry, scratch this, I got confused by THERMAL_TEMP_INVALID
> > > showing
> > > up in
> > > sysfs, but it did show up before too.
> > >
> > > Please test!
> > >
> >
> > >
> >
> > >
> > It will be easy if you have some test branch to avoid dependecies
> > on
> > other patches.
>
> Please see the thermal-intel-test branch in linux-pm.git. It's this
> series on top of the core thermal stuff + ARM drivers.
Tested on one system. Works fine.
Thanks,
Srinivas
next prev parent reply other threads:[~2023-01-23 21:35 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 ` [PATCH v7 0/3] thermal: intel: Use generic trip points in 2 drivers Rafael J. Wysocki
2023-01-23 18:52 ` 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 [this message]
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=ca878d5a177b68eaf5f698e0afda5c0b1718a53f.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--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