linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Balakrishnan, Anand" <anandbal@lab126.com>
To: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"amit.kachhap@gmail.com" <amit.kachhap@gmail.com>,
	"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
	"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
	"amit.kucheria@verdurent.com" <amit.kucheria@verdurent.com>
Cc: "Healy, Christopher" <healych@amazon.com>
Subject: correct source tree to make contributions to Linux thermal framework
Date: Thu, 11 Nov 2021 18:42:10 +0000	[thread overview]
Message-ID: <1636656130551.5237@lab126.com> (raw)
In-Reply-To: <YYvuAU+d3TAS6fI7@kroah.com>

Hello folks,

At our company, we maintain an internal thermal framework patch. We are exploring the option to up-stream this patch so we don't have to keep porting this from one Kernel version to the other. Looking for advise on the right device tree to get started.
Thermal framework code resides here: https://elixir.bootlin.com/linux/latest/source/drivers/thermal. What is the correct source tree we should use from https://git.kernel.org/??

Thanks,
Anand


       reply	other threads:[~2021-11-11 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1636488946043.43408@lab126.com>
     [not found] ` <YYvuAU+d3TAS6fI7@kroah.com>
2021-11-11 18:42   ` Balakrishnan, Anand [this message]
2021-11-11 19:09     ` correct source tree to make contributions to Linux thermal framework Daniel Lezcano
2021-11-12 22:14       ` Balakrishnan, Anand
2021-11-13  8:26         ` Daniel Lezcano
2021-11-18 19:19           ` Balakrishnan, Anand

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=1636656130551.5237@lab126.com \
    --to=anandbal@lab126.com \
    --cc=amit.kachhap@gmail.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=healych@amazon.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=viresh.kumar@linaro.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).