linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: Greg KH <gregkh@linuxfoundation.org>, Kant Fan <kant@allwinnertech.com>
Cc: rui.zhang@intel.com, daniel.lezcano@linaro.org,
	javi.merino@kernel.org, edubezval@gmail.com, orjan.eide@arm.com,
	amitk@kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	allwinner-opensource-support@allwinnertech.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] thermal: devfreq_cooling: use local ops instead of global ops
Date: Tue, 29 Mar 2022 12:24:56 +0100	[thread overview]
Message-ID: <cebde4f1-b3ec-dc46-dd17-a7162316aeb2@arm.com> (raw)
In-Reply-To: <YkLrZ9OkJz2R8tU6@kroah.com>



On 3/29/22 12:20, Greg KH wrote:
> On Fri, Mar 25, 2022 at 05:44:36PM +0800, Kant Fan wrote:
>> commit 7b62935828266658714f81d4e9176edad808dc70 upstream.
> 
> I do not see this commit in Linus's tree :(
> 
> confused,
> 
> greg k-h

My apologies Greg, I missed that.

We need to first get the patch [1] into upstream.
Kant would resend this patch after that happen.

[1] 
https://lore.kernel.org/linux-pm/20220325073030.91919-1-kant@allwinnertech.com/

  reply	other threads:[~2022-03-29 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  9:44 [PATCH] thermal: devfreq_cooling: use local ops instead of global ops Kant Fan
2022-03-29  6:59 ` Lukasz Luba
2022-04-19 15:49   ` Kant Fan
2022-04-20 10:32     ` Lukasz Luba
2022-04-23 10:49       ` Kant Fan
2022-03-29 11:20 ` Greg KH
2022-03-29 11:24   ` Lukasz Luba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-12  4:59 Kant Fan
2022-03-14 13:41 ` Lukasz Luba
2022-03-25 10:43   ` Kant Fan
2022-03-29  6:39     ` Lukasz Luba

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=cebde4f1-b3ec-dc46-dd17-a7162316aeb2@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=allwinner-opensource-support@allwinnertech.com \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=javi.merino@kernel.org \
    --cc=kant@allwinnertech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=orjan.eide@arm.com \
    --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).