All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine Tenart <atenart@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	amitk@kernel.org, rui.zhang@intel.com
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: Wed, 20 Oct 2021 15:38:27 +0200	[thread overview]
Message-ID: <163473710782.3319.6254396851923671939@kwain> (raw)
In-Reply-To: <03ba2e41-6ae6-d4ee-ace5-055ac40c1128@linaro.org>

Hello Daniel,

Quoting Daniel Lezcano (2021-09-24 19:40:13)
> 
> 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.

I don't see it in thermal/next even though patch 1 has made it. Not sure
if patch 2 has slipped through the cracks or wasn't pushed yet. If it's
the later, please ignore this mail.

Thanks!
Antoine

  parent reply	other threads:[~2021-10-20 13:38 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
2021-10-20 13:38       ` Antoine Tenart [this message]
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=163473710782.3319.6254396851923671939@kwain \
    --to=atenart@kernel.org \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.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 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.