Request: Add Transition TI Tree to linux-next

Request: Add Transition TI Tree to linux-next

[Nishanth Menon]

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

Hi Stephen,

We have been working towards a rotating maintainership for various
TI dts and potentially related areas that Santosh is currently
maintaining. As part of this, my tree[1] is now integrated into the
common effort.

Please replace my current tree[1] with:

   git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git#ti-next

We will follow the usual rules (GPLv2, contributer's guidelines,
reviews, successfully tested, meant for next merge window and intent
towards linus's tree via submaintainers) and this would be a rebased
tree as needed.

[1]
git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git#ti-k3-next (ti-k3-new)

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Request: Add Transition TI Tree to linux-next

[Stephen Rothwell]

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

Hi Nishanth,

On Sat, 20 Nov 2021 21:25:48 -0600 Nishanth Menon <nm@ti.com> wrote:
>
> We have been working towards a rotating maintainership for various
> TI dts and potentially related areas that Santosh is currently
> maintaining. As part of this, my tree[1] is now integrated into the
> common effort.
> 
> Please replace my current tree[1] with:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git#ti-next
> 
> We will follow the usual rules (GPLv2, contributer's guidelines,
> reviews, successfully tested, meant for next merge window and intent
> towards linus's tree via submaintainers) and this would be a rebased
> tree as needed.
> 
> [1]
> git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git#ti-k3-next (ti-k3-new)

All done.  Tero Kristo was listed as the contact for that tree, and now
you are both, along with Santosh contacts for the new tree called "ti".

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

-- 
Cheers,
Stephen Rothwell

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

Re: Request: Add Transition TI Tree to linux-next

[Stephen Rothwell]

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

Hi all,

On Wed, 19 Aug 2020 07:11:37 -0500 Nishanth Menon <nm@ti.com> wrote:
> 
> Could you add my ti-k3-next branch to linux-next? You can find it
> here:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git#ti-k3-next
> 
> NOTE: This tree will eventually supersede Tero's tree[1] which is
> currently in linux-next.

Added from today.  I have called it ti-k3-new for now.

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

Request: Add Transition TI Tree to linux-next

[Nishanth Menon]

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

Hi Stephen,

Could you add my ti-k3-next branch to linux-next? You can find it
here:

git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git#ti-k3-next

NOTE: This tree will eventually supersede Tero's tree[1] which is
currently in linux-next.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

[1] {old tree} git://git.kernel.org/pub/scm/linux/kernel/git/kristo/linux.git#ti-k3-next

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]