Hi Lucas, On Tue, 20 Feb 2024 23:29:54 -0600 Lucas De Marchi <lucas.demarchi@xxxxxxxxx> wrote: > > Looking at https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2d5c7b7eb345249cb34d42cbc2b97b4c57ea944e > it seems we still don't have drm-xe-next branch in linux-next. > > Stephen, could you please add it? Or do I have to do something on my end > before that? This is the branch: > > https://gitlab.freedesktop.org/drm/xe/kernel drm-xe-next Added from tomorrow. Currently the only contact is yourself. Do you want anyone else (or a mailing list) as well? Do you want the drm-xe-fixes branch included as well? 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:
pgpUXI3oSzvT7.pgp
Description: OpenPGP digital signature
