Hi Catalin,
On Thu, 1 Mar 2018 17:58:53 +0000 Catalin Marinas <catalin.marinas@xxxxxxx> wrote:
>
> Could you please add another arm64 branch to linux-next:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux for-next/fixes
>
> We currently have for-next/core which is the preparation for the
> next merging window and it is usually based on rc3/rc4 in the current
> cycle. The for-next/fixes is used for fixes during the rcX cycles
> independent of the for-next/core. While the lifetime of a patch in
> for-next/fixes is relatively small (usually up to a week), it's still
> useful to get a heads up on conflicts or just have a fix early in -next
> before it hits mainline.
>
> (Will and I also take turns on who's managing which branch)
Added from today. I also added Will as a second contact for the arm64
tree.
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@xxxxxxxxxxxxxxxx
Attachment:
pgpog6Hqyed7w.pgp
Description: OpenPGP digital signature
