* Please add two new branches for sophgo/linux.git
@ 2025-05-06 3:36 Chen Wang
2025-05-06 12:42 ` Stephen Rothwell
0 siblings, 1 reply; 2+ messages in thread
From: Chen Wang @ 2025-05-06 3:36 UTC (permalink / raw)
To: linux-next@vger•kernel.org >> Linux Next Mailing List,
Stephen Rothwell
Cc: Inochi Amaoto, sophgo, Chen Wang
Hi, Stephen,
We already have two branches for-next & fixes included in linux-next for
collecting DTS related patches for exiting tree:
https://github.com/sophgo/linux.git.
Now I want to include two new branches in the linux-next to collect
drivers/soc related patches.
branch for soc master: soc-for-next
branch for soc pending-fixes: soc-fixes
The patches in these braches will be sent to Arnd Bergmann and
soc@kernel•org.
Thanks,
Chen
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Please add two new branches for sophgo/linux.git
2025-05-06 3:36 Please add two new branches for sophgo/linux.git Chen Wang
@ 2025-05-06 12:42 ` Stephen Rothwell
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2025-05-06 12:42 UTC (permalink / raw)
To: Chen Wang; +Cc: Linux Next Mailing List, Inochi Amaoto, sophgo
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
Hi Chen,
On Tue, 6 May 2025 11:36:52 +0800 Chen Wang <unicorn_wang@outlook•com> wrote:
>
> We already have two branches for-next & fixes included in linux-next
> for collecting DTS related patches for exiting tree:
> https://github.com/sophgo/linux.git.
>
> Now I want to include two new branches in the linux-next to collect
> drivers/soc related patches.
>
> branch for soc master: soc-for-next
>
> branch for soc pending-fixes: soc-fixes
>
> The patches in these braches will be sent to Arnd Bergmann and
> soc@kernel•org.
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.
--
Cheers,
Stephen Rothwell
sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-05-06 12:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-05-06 3:36 Please add two new branches for sophgo/linux.git Chen Wang
2025-05-06 12:42 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox