From: "Balakrishnan, Anand" <anandbal@lab126.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
"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>,
"amit.kucheria@verdurent.com" <amit.kucheria@verdurent.com>
Cc: "Healy, Christopher" <healych@amazon.com>
Subject: Re: correct source tree to make contributions to Linux thermal framework
Date: Fri, 12 Nov 2021 22:14:54 +0000 [thread overview]
Message-ID: <1636755294516.66191@lab126.com> (raw)
In-Reply-To: <5007f2fd-285c-73fd-21a9-ab0029578d4a@linaro.org>
Hey Daniel,
Thank you for for the information. In the future, If I have to find this information by myself, is there a document for this?
I was looking at https://www.kernel.org/doc/linux/MAINTAINERS and there are several references to thermal here, but I did not see any mention of the tree you pointed me to.
Thanks,
Anand
________________________________________
From: Daniel Lezcano <daniel.lezcano@linaro.org>
Sent: Thursday, November 11, 2021 11:09 AM
To: Balakrishnan, Anand; linux-pm@vger.kernel.org; amit.kachhap@gmail.com; viresh.kumar@linaro.org; amit.kucheria@verdurent.com
Cc: Healy, Christopher
Subject: RE: [EXTERNAL] correct source tree to make contributions to Linux thermal framework
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On 11/11/2021 19:42, Balakrishnan, Anand wrote:
> 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/??
https://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git/
branch : next
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2021-11-12 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 20:15 correct source tree to make contributions to Linux thermal framework Balakrishnan, Anand
2021-11-10 16:06 ` Greg KH
2021-11-11 18:42 ` Balakrishnan, Anand
2021-11-11 19:09 ` Daniel Lezcano
2021-11-12 22:14 ` Balakrishnan, Anand [this message]
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=1636755294516.66191@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 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.