On Fri, Jun 21, 2024 at 03:45:15PM +1000, Stephen Rothwell wrote:
> Hi Mark,
>
> I received the below request from Tejun. Please add this tree (from
> the next git repo dir) using
>
> ../tools/add_repo sched-ext korg:tj/sched_ext.git for-next
>
> then add this line to etc/control (just after the workqueues line):
>
> Tejun Heo <tj@xxxxxxxxxx> git sched-ext git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git for-next no
>
> Note the TABs between fields ...
Should be there tday.
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.
Attachment:
signature.asc
Description: PGP signature
