From: AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: MediaTek for-next: Replace matthias.bgg tree with mediatek
Date: Thu, 8 Feb 2024 10:07:54 +0100 [thread overview]
Message-ID: <478be18c-a242-4004-b45d-8aaf7505588f@kernel.org> (raw)
In-Reply-To: <20240208070222.3a916478@canb.auug.org.au>
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@gmail.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
prev parent reply other threads:[~2024-02-08 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 10:08 MediaTek for-next: Replace matthias.bgg tree with mediatek AngeloGioacchino Del Regno
2024-02-06 22:05 ` Stephen Rothwell
2024-02-07 16:08 ` Matthias Brugger
2024-02-07 20:02 ` Stephen Rothwell
2024-02-08 9:07 ` AngeloGioacchino Del Regno [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=478be18c-a242-4004-b45d-8aaf7505588f@kernel.org \
--to=angelogioacchino.delregno@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthias.bgg@gmail.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
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).