Please include the sched_ext:for-next branch in linux-next

Please include the sched_ext:for-next branch in linux-next

[Tejun Heo]

Hello, Stephen.

It's been decided that sched_ext will be pulled during the next merge
window:

  https://lore.kernel.org/all/CAHk-=wg8APE61e5Ddq5mwH55Eh0ZLDV4Tr+c6_gFS7g2AxnuHQ@mail.gmail.com/

Can you please include the following branch in linux-next so that it can
receive appropriate testing? It creates a trivial merge conflict in
MAINTAINERS but otherwise merges cleanly.

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git for-next

Thank you.

-- 
tejun

Re: Please include the sched_ext:for-next branch in linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

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@kernel.org>	git	sched-ext git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git	for-next	no

Note the TABs between fields ...

On Tue, 18 Jun 2024 11:34:32 -1000 Tejun Heo <tj@kernel.org> wrote:
>
> Hello, Stephen.
> 
> It's been decided that sched_ext will be pulled during the next merge
> window:
> 
>   https://lore.kernel.org/all/CAHk-=wg8APE61e5Ddq5mwH55Eh0ZLDV4Tr+c6_gFS7g2AxnuHQ@mail.gmail.com/
> 
> Can you please include the following branch in linux-next so that it can
> receive appropriate testing? It creates a trivial merge conflict in
> MAINTAINERS but otherwise merges cleanly.
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git for-next
> 
> Thank you.
> 
> -- 
> tejun

Then reply to Tejun to let then know when it is in.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Please include the sched_ext:for-next branch in linux-next

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]

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@kernel.org>	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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Please include the sched_ext:for-next branch in linux-next

[Tejun Heo]

Hello,

On Fri, Jun 21, 2024 at 12:09:47PM +0100, Mark Brown wrote:
> 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@kernel.org>	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.

-- 
tejun