Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	Eduardo Valentin <edubezval@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>
Subject: Re: Adding thermal group git tree
Date: Wed, 16 Oct 2019 10:48:42 +0200
Message-ID: <53defc08-9f67-ecdd-eb77-c0f34fecf05a@linaro.org> (raw)
In-Reply-To: <20191015075154.4858a256@canb.auug.org.au>

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

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 18:30 Daniel Lezcano
2019-10-14 20:51 ` Stephen Rothwell
2019-10-16  8:48   ` Daniel Lezcano [this message]
2019-10-17  1:40     ` Zhang Rui
2019-10-17 20:40       ` Stephen Rothwell
2019-10-18  2:31         ` Zhang Rui
2019-10-17  6:28 ` Daniel Lezcano
2019-10-17 20:45   ` Stephen Rothwell

Reply instructions:

You may reply publically 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=53defc08-9f67-ecdd-eb77-c0f34fecf05a@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git