Include in next: spacemit/linux
Hi Stephen,
Please kindly include spacemit/linux tree into the linux-next:
https://github.com/spacemit-com/linux
branch for master: for-next
branch for pending-fixes: fixes
Repo will be use for collecting patches for SpacemiT's SoC which recently I took over:
https://lore.kernel.org/r/[email protected]
The patches in the tree will be sent to Arnd Bergmann and [email protected].
Best regards,
Signature · 3 lines
Yixun Lan (dlan) Gentoo Linux Developer GPG Key ID AABEFD55
Hi,
Quoted 7 lines · On Tue, 29 Oct 2024 12:53:26 +0800 Yixun Lan <[email protected]> wrote:
Please kindly include spacemit/linux tree into the linux-next:
https://github.com/spacemit-com/linux
branch for master: for-next
Quoted 8 lines
branch for pending-fixes: fixes
Repo will be use for collecting patches for SpacemiT's SoC which recently I took over:
https://lore.kernel.org/r/[email protected]
The patches in the tree will be sent to Arnd Bergmann and [email protected].
Added from tomorrow.
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]
Hi Stephen:
Quoted 35 lines · Stephen Rothwell
Hi,
Quoted 7 lines · On Tue, 29 Oct 2024 12:53:26 +0800 Yixun Lan <[email protected]> wrote:
Please kindly include spacemit/linux tree into the linux-next:
https://github.com/spacemit-com/linux
branch for master: for-next
Quoted 8 lines
branch for pending-fixes: fixes
Repo will be use for collecting patches for SpacemiT's SoC which recently I took over:
https://lore.kernel.org/r/[email protected]
The patches in the tree will be sent to Arnd Bergmann and [email protected].
Added from tomorrow.
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.
Yes, I understand and thanks for all the info..
Signature · 3 lines
Yixun Lan (dlan) Gentoo Linux Developer GPG Key ID AABEFD55