Adding thermal group git tree

Adding thermal group git tree

[Daniel Lezcano]

Hi Stephen,

we decided to consolidate the thermal tree into a group which becomes
the reference for the thermal subsystem.

Patches are reviewed and tested with kernelci in a bleeding edge branch
and then merged to the linux-next branch.

Is it possible to add the thermal/linux-next branch to the linux-tree?

git://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git
thermal/linux-next

Thanks in advance

  -- Daniel


-- 
 <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

Re: Adding thermal group git tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

Hi Daniel,

On Fri, 11 Oct 2019 20:30:33 +0200 Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> we decided to consolidate the thermal tree into a group which becomes
> the reference for the thermal subsystem.
> 
> Patches are reviewed and tested with kernelci in a bleeding edge branch
> and then merged to the linux-next branch.
> 
> Is it possible to add the thermal/linux-next branch to the linux-tree?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git
> thermal/linux-next

OK, I have added this from today.  I renamed the previous thermal tree
to be thermal-zhang.  Currently you are the only contact for this new
thermal tree, let me know if you want any others added.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Adding thermal group git tree

[Daniel Lezcano]

[-- Attachment #1.1: Type: text/plain, Size: 1988 bytes --]


Hi Stephen,

thanks for adding the branch. I'll let Eduardo and Rui tell if they want
to be cc'ed.


On 14/10/2019 22:51, Stephen Rothwell wrote:
> Hi Daniel,
> 
> On Fri, 11 Oct 2019 20:30:33 +0200 Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>>
>> we decided to consolidate the thermal tree into a group which becomes
>> the reference for the thermal subsystem.
>>
>> Patches are reviewed and tested with kernelci in a bleeding edge branch
>> and then merged to the linux-next branch.
>>
>> Is it possible to add the thermal/linux-next branch to the linux-tree?
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git
>> thermal/linux-next
> 
> OK, I have added this from today.  I renamed the previous thermal tree
> to be thermal-zhang.  Currently you are the only contact for this new
> thermal tree, let me know if you want any others added.



> Thanks for adding your subsystem tree as a participant of linux-next.  As
> you may know, this is not a judgement of your code.  The purpose of
> linux-next is for integration testing and to lower the impact of
> conflicts between subsystems in the next merge window. 
> 
> You will need to ensure that the patches/commits in your tree/series have
> been:
>      * submitted under GPL v2 (or later) and include the Contributor's
>         Signed-off-by,
>      * posted to the relevant mailing list,
>      * reviewed by you (or another maintainer of your subsystem tree),
>      * successfully unit tested, and 
>      * destined for the current or next Linux merge window.
> 
> Basically, this should be just what you would send to Linus (or ask him
> to fetch).  It is allowed to be rebased if you deem it necessary.
> 


-- 
 <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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: Adding thermal group git tree

[Zhang Rui]

On Wed, 2019-10-16 at 10:48 +0200, Daniel Lezcano wrote:
> Hi Stephen,
> 
> thanks for adding the branch. I'll let Eduardo and Rui tell if they
> want
> to be cc'ed.

Hi, Stephen,

Thanks for adding the branch, and yes, please CC Eduardo and me. Thanks
a lot!

-rui
> 
> 
> On 14/10/2019 22:51, Stephen Rothwell wrote:
> > Hi Daniel,
> > 
> > On Fri, 11 Oct 2019 20:30:33 +0200 Daniel Lezcano <
> > daniel.lezcano@linaro.org> wrote:
> > > 
> > > we decided to consolidate the thermal tree into a group which
> > > becomes
> > > the reference for the thermal subsystem.
> > > 
> > > Patches are reviewed and tested with kernelci in a bleeding edge
> > > branch
> > > and then merged to the linux-next branch.
> > > 
> > > Is it possible to add the thermal/linux-next branch to the linux-
> > > tree?
> > > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/thermal/linux.git
> > > thermal/linux-next
> > 
> > OK, I have added this from today.  I renamed the previous thermal
> > tree
> > to be thermal-zhang.  Currently you are the only contact for this
> > new
> > thermal tree, let me know if you want any others added.
> 
> 
> 
> > Thanks for adding your subsystem tree as a participant of linux-
> > next.  As
> > you may know, this is not a judgement of your code.  The purpose of
> > linux-next is for integration testing and to lower the impact of
> > conflicts between subsystems in the next merge window. 
> > 
> > You will need to ensure that the patches/commits in your
> > tree/series have
> > been:
> >      * submitted under GPL v2 (or later) and include the
> > Contributor's
> >         Signed-off-by,
> >      * posted to the relevant mailing list,
> >      * reviewed by you (or another maintainer of your subsystem
> > tree),
> >      * successfully unit tested, and 
> >      * destined for the current or next Linux merge window.
> > 
> > Basically, this should be just what you would send to Linus (or ask
> > him
> > to fetch).  It is allowed to be rebased if you deem it necessary.
> > 
> 
> 

Re: Adding thermal group git tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 219 bytes --]

Hi Zhang,

On Thu, 17 Oct 2019 09:40:06 +0800 Zhang Rui <rui.zhang@intel.com> wrote:
>
> Thanks for adding the branch, and yes, please CC Eduardo and me. Thanks
> a lot!

Done.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Adding thermal group git tree

[Zhang Rui]

On Fri, 2019-10-18 at 07:40 +1100, Stephen Rothwell wrote:
> Hi Zhang,
> 
> On Thu, 17 Oct 2019 09:40:06 +0800 Zhang Rui <rui.zhang@intel.com>
> wrote:
> > 
> > Thanks for adding the branch, and yes, please CC Eduardo and me.
> > Thanks
> > a lot!
> 
> Done.

Great, thanks for your help!

-rui
> 

Re: Adding thermal group git tree

[Daniel Lezcano]

[-- Attachment #1.1: Type: text/plain, Size: 221 bytes --]


H Stephen,

is it possible to replace the current monitored branch clockevents/next
by timers/drivers/next ?

From https://git.linaro.org/people/daniel.lezcano/linux.git

Thanks in advance

 -- Daniel





[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: Adding thermal group git tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 316 bytes --]

Hi Daniel,

On Thu, 17 Oct 2019 08:28:41 +0200 Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
> is it possible to replace the current monitored branch clockevents/next
> by timers/drivers/next ?
> 
> From https://git.linaro.org/people/daniel.lezcano/linux.git

Done.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]