From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Antoine Tenart <atenart@kernel.org>,
rui.zhang@intel.com, amitk@kernel.org
Cc: linux-pm@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] thermal: int340x: do not set a wrong tcc offset on resume
Date: Fri, 24 Sep 2021 10:51:35 -0700 [thread overview]
Message-ID: <9d1eb69d6b498856e193f86b117665c868425d17.camel@linux.intel.com> (raw)
In-Reply-To: <03ba2e41-6ae6-d4ee-ace5-055ac40c1128@linaro.org>
On Fri, 2021-09-24 at 19:40 +0200, Daniel Lezcano wrote:
> On 24/09/2021 18:27, Srinivas Pandruvada wrote:
> > Hi Daniel,
> >
> > This patch is important. Can we send for 5.15 rc release?
> >
> > I see the previous version of this patch is applied to linux-next.
> > But this series is better as it splits into two patches. The first
> > one
> > can be easily backported and will fix the problem. The second one
> > is an
> > improvement.
>
> Yes, it is in the pipe.
>
> I've applied the patch 1/2 to the fixes branch and the patch 2/2 will
> land in the next branch as soon as the next -rc is released with the
> fix
> and merged to the next branch.
Thanks Daniel.
-Srinivas
>
>
next prev parent reply other threads:[~2021-09-24 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 8:56 [PATCH v2 0/2] thermal: int340x: fix tcc offset on resume Antoine Tenart
2021-09-09 8:56 ` [PATCH v2 1/2] thermal: int340x: do not set a wrong " Antoine Tenart
2021-09-24 16:27 ` Srinivas Pandruvada
2021-09-24 17:40 ` Daniel Lezcano
2021-09-24 17:51 ` Srinivas Pandruvada [this message]
2021-10-20 13:38 ` Antoine Tenart
2021-10-21 9:47 ` Daniel Lezcano
2021-10-21 10:02 ` Antoine Tenart
2021-09-09 8:56 ` [PATCH v2 2/2] thermal: int340x: improve the tcc offset saving for suspend/resume Antoine Tenart
2021-09-09 9:35 ` [PATCH v2 0/2] thermal: int340x: fix tcc offset on resume Srinivas Pandruvada
2021-09-17 7:56 ` Daniel Lezcano
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=9d1eb69d6b498856e193f86b117665c868425d17.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=amitk@kernel.org \
--cc=atenart@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).