From: Yixun Lan <dlan@gentoo.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Conor Dooley <conor@kernel.org>,
Inochi Amaoto <inochiama@outlook.com>,
Jesse Taube <mr.bossman075@gmail.com>,
soc@kernel.org
Subject: Re: Include in next: spacemit/linux
Date: Tue, 29 Oct 2024 14:43:44 +0800 [thread overview]
Message-ID: <20241029064344-GYB97300@gentoo> (raw)
In-Reply-To: <20241029173322.4d879601@canb.auug.org.au>
Hi Stephen:
On 17:33 Tue 29 Oct , Stephen Rothwell wrote:
> Hi,
>
> On Tue, 29 Oct 2024 12:53:26 +0800 Yixun Lan <dlan@gentoo.org> wrote:
> >
> > 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/20241028-00-k1-maintainer-v2-1-272c9834220d@gentoo.org
> >
> > The patches in the tree 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.
>
Yes, I understand and thanks for all the info..
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
prev parent reply other threads:[~2024-10-29 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 4:53 Include in next: spacemit/linux Yixun Lan
2024-10-29 6:33 ` Stephen Rothwell
2024-10-29 6:43 ` Yixun Lan [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=20241029064344-GYB97300@gentoo \
--to=dlan@gentoo.org \
--cc=conor@kernel.org \
--cc=inochiama@outlook.com \
--cc=linux-next@vger.kernel.org \
--cc=mr.bossman075@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=soc@kernel.org \
/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