Skip to contentSkip to conversation

MediaTek for-next: Replace matthias.bgg tree with mediatek

DISCUSSION AngeloGioacchino Del Regno 3 participants 5 messages Feb 6, 2024 – Feb 8, 2024 Linux-next tree

lore
Share & tools
lore
#0 lore raw

Hello Stephen,

A while ago we migrated the MediaTek SoC trees from Matthias' GIT repo to the new MediaTek collaborative one. I just noticed that the linux-next branch didn't get replaced (we didn't tell you anything about it, so that's our bad!).

Can you please replace the tracked for-next branch?

...The old one, to remove, is:
git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git#for-next

...the new one, to add, is:
git://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git#for-next

Thanks!
Angelo

#1 lore raw

Hi Angelo,

Quoted 5 lines · On Tue, 6 Feb 2024 11:08:25 +0100 AngeloGioacchino Del Regno…

A while ago we migrated the MediaTek SoC trees from Matthias' GIT repo to the new MediaTek collaborative one. I just noticed that the linux-next branch didn't get replaced (we didn't tell you anything about it, so that's our bad!).

Quoted 7 lines

Can you please replace the tracked for-next branch?

...The old one, to remove, is:
git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git#for-next

...the new one, to add, is:
git://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git#for-next

Done.

I have only Matthias listed as a contact for that tree, should I add anyone else?

Signature · 2 lines
Cheers,
Stephen Rothwell
#2 lore raw

Hi Stephen,

Quoted 13 lines · Stephen Rothwell

Hi Angelo,

Quoted 10 lines · On Tue, 6 Feb 2024 11:08:25 +0100 AngeloGioacchino Del Regno…

A while ago we migrated the MediaTek SoC trees from Matthias' GIT repo to the new MediaTek collaborative one. I just noticed that the linux-next branch didn't get replaced (we didn't tell you anything about it, so that's our bad!).

Can you please replace the tracked for-next branch?

...The old one, to remove, is:
git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git#for-next

Quoted 8 lines
Quoted 2 lines

...the new one, to add, is:
git://git.kernel.org/pub/scm/linux/kernel/git/mediatek/linux.git#for-next

Done.

I have only Matthias listed as a contact for that tree, should I add anyone else?

Please add Angelo to the contact list.

Thanks a lot,
Matthias

#3 lore raw

Hi Matthias,

Quoted 2 lines · On Wed, 7 Feb 2024 16:08:22 +0000 Matthias Brugger <[email protected]>…

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.

Signature · 7 lines
Cheers,
Stephen Rothwell 
[email protected]

-- 
Cheers,
Stephen Rothwell
#4 lore raw

Il 07/02/24 21:02, Stephen Rothwell ha scritto:

Quoted 24 lines

Hi Matthias,

Quoted 2 lines · On Wed, 7 Feb 2024 16:08:22 +0000 Matthias Brugger <[email protected]>…

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.

Quoted 3 lines

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