[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <478be18c-a242-4004-b45d-8aaf7505588f@kernel.org>
Date: Thu, 8 Feb 2024 10:07:54 +0100
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Matthias Brugger <matthias.bgg@...il.com>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: MediaTek for-next: Replace matthias.bgg tree with mediatek
Il 07/02/24 21:02, Stephen Rothwell ha scritto:
> Hi Matthias,
>
> On Wed, 7 Feb 2024 16:08:22 +0000 Matthias Brugger <matthias.bgg@...il.com> wrote:
>>
>> Please add Angelo to the contact list.
>
> Done
>
> For Angelo's benefit:
>
> 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.
>
Thank you, Stephen!
Cheers,
Angelo
Powered by blists - more mailing lists