From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: Tejun Heo <tj@kernel.org>,
linux-next@vger.kernel.org, David Vernet <dvernet@meta.com>
Subject: Re: Please include the sched_ext:for-next branch in linux-next
Date: Fri, 21 Jun 2024 15:45:15 +1000 [thread overview]
Message-ID: <20240621154515.53aff781@canb.auug.org.au> (raw)
In-Reply-To: <ZnH9aHFOl4wufXkQ@slm.duckdns.org>
[-- 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 --]
next prev parent reply other threads:[~2024-06-21 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 21:34 Please include the sched_ext:for-next branch in linux-next Tejun Heo
2024-06-21 5:45 ` Stephen Rothwell [this message]
2024-06-21 11:09 ` Mark Brown
2024-06-21 19:02 ` Tejun Heo
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=20240621154515.53aff781@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=broonie@kernel.org \
--cc=dvernet@meta.com \
--cc=linux-next@vger.kernel.org \
--cc=tj@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