Skip to contentSkip to conversation

updated Amlogic repo used for linux-next

PATCH Kevin Hilman 4 participants 5 messages May 27, 2021 – May 31, 2021

Subsystems (2)
Linux-next tree Arm/Amlogic Meson SoC support
lore
Share & tools
lore

Kevin Hilman

author maintainer
#0 lore raw

Hi Stephen,

Please update the tree used for Amlogic SoC kernel development (suggested patch below[1].)

We've switched to a maintainer group for this tree which is now co-maintained by myself and Neil (cc'd)

Thank you,

Kevin & Neil

[1]

Next/Trees +1 -1
index 2d22ca1d2911..1794b9144f3a 100644
@@ -103,7 +103,7 @@ arm64		git	git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/co
 arm-perf		git	git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git#for-next/perf
 arm-soc		git	git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git#for-next
 actions		git	git://git.kernel.org/pub/scm/linux/kernel/git/mani/linux-actions.git#for-next
-amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next
+amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git#for-next
 aspeed		git	git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git#for-next
 at91		git	git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-next
 drivers-memory	git	https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git#for-next
#1 lore raw

Hi Kevin,

Quoted 13 lines · On Thu, 27 May 2021 11:36:50 -0700 Kevin Hilman <[email protected]> wrote:

Please update the tree used for Amlogic SoC kernel development (suggested patch below[1].)

We've switched to a maintainer group for this tree which is now co-maintained by myself and Neil (cc'd)

[1]

Next/Trees +0 -0
index 2d22ca1d2911..1794b9144f3a 100644

Next/Trees arm64 git git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/co · line 109

Quoted 8 lines
Next/Trees +1 -1
@@ -103,7 +103,7 @@ arm64		git	git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/co
 arm-perf		git	git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git#for-next/perf
 arm-soc		git	git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git#for-next
 actions		git	git://git.kernel.org/pub/scm/linux/kernel/git/mani/linux-actions.git#for-next
-amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next
+amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git#for-next
 aspeed		git	git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git#for-next
 at91		git	git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-next
 drivers-memory	git	https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git#for-next

I have updated the tree URL and added Neil as a contact. I still have Carlo (cc'd) listed as a contact, is that correct?

[The following for Neil'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 · 3 lines
Cheers,
Stephen Rothwell 
[email protected]
author maintainer
#2 lore raw
Quoted 10 lines · Stephen Rothwell

Hi Kevin,

Quoted 7 lines · On Thu, 27 May 2021 11:36:50 -0700 Kevin Hilman <[email protected]> wrote:

Please update the tree used for Amlogic SoC kernel development (suggested patch below[1].)

We've switched to a maintainer group for this tree which is now co-maintained by myself and Neil (cc'd)

Quoted 16 lines
Quoted 6 lines

[1]

Next/Trees +0 -0
index 2d22ca1d2911..1794b9144f3a 100644

Next/Trees arm64 git git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/co · line 109

Quoted 8 lines
Next/Trees +1 -1
@@ -103,7 +103,7 @@ arm64		git	git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/co
 arm-perf		git	git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git#for-next/perf
 arm-soc		git	git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git#for-next
 actions		git	git://git.kernel.org/pub/scm/linux/kernel/git/mani/linux-actions.git#for-next
-amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next
+amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git#for-next
 aspeed		git	git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git#for-next
 at91		git	git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-next
 drivers-memory	git	https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git#for-next

I have updated the tree URL and added Neil as a contact.

Thank you.

Quoted 1 line

I still have Carlo (cc'd) listed as a contact, is that correct?

You can drop Carlo. He stepped down as co-maintainer awhile back.

Thanks,

Kevin

#3 lore raw

Hi Kevin,

Quoted 4 lines · On Fri, 28 May 2021 11:32:01 -0700 Kevin Hilman <[email protected]> wrote:
Quoted 2 lines

I still have Carlo (cc'd) listed as a contact, is that correct?

You can drop Carlo. He stepped down as co-maintainer awhile back.

Done.

Signature · 2 lines
Cheers,
Stephen Rothwell
#4 lore raw
In reply to Stephen Rothwell
Quoted 44 lines · Stephen Rothwell

Hi Kevin,

Quoted 13 lines · On Thu, 27 May 2021 11:36:50 -0700 Kevin Hilman <[email protected]> wrote:

Please update the tree used for Amlogic SoC kernel development (suggested patch below[1].)

We've switched to a maintainer group for this tree which is now co-maintained by myself and Neil (cc'd)

[1]

Next/Trees +0 -0
index 2d22ca1d2911..1794b9144f3a 100644

Next/Trees arm64 git git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/co · line 109

Quoted 8 lines
Next/Trees +1 -1
@@ -103,7 +103,7 @@ arm64		git	git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux#for-next/co
 arm-perf		git	git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git#for-next/perf
 arm-soc		git	git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git#for-next
 actions		git	git://git.kernel.org/pub/scm/linux/kernel/git/mani/linux-actions.git#for-next
-amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next
+amlogic		git	git://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git#for-next
 aspeed		git	git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git#for-next
 at91		git	git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-next
 drivers-memory	git	https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git#for-next

I have updated the tree URL and added Neil as a contact. I still have Carlo (cc'd) listed as a contact, is that correct?

[The following for Neil'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.

Noted !

Thanks,
Neil