From: Greg KH <greg@kroah.com>
To: "Balakrishnan, Anand" <anandbal@lab126.com>
Cc: "Healy, Christopher" <healych@amazon.com>,
"kernelnewbies@kernelnewbies.org"
<kernelnewbies@kernelnewbies.org>
Subject: Re: correct source tree to make contributions to Linux thermal framework
Date: Wed, 10 Nov 2021 17:06:25 +0100 [thread overview]
Message-ID: <YYvuAU+d3TAS6fI7@kroah.com> (raw)
In-Reply-To: <1636488946043.43408@lab126.com>
On Tue, Nov 09, 2021 at 08:15:46PM +0000, Balakrishnan, Anand wrote:
> Hello Developers,
>
>
> 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.
>
> 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/??
Use the tool, scripts/get_maintainer.pl on your patch and it will
identify the subsystem and mailing list where you need to send your
change to.
If you work off of the linux-next branch, that is a good start as that
contains a sum of all kernel maintainer's tree, as the
Documentation/process/ document explains, and is the easiest to work off
of to start with.
Hope this helps,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2021-11-10 16:06 UTC|newest]
Thread overview: 2+ 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 [this message]
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=YYvuAU+d3TAS6fI7@kroah.com \
--to=greg@kroah.com \
--cc=anandbal@lab126.com \
--cc=healych@amazon.com \
--cc=kernelnewbies@kernelnewbies.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).