From: Tejun Heo <tj@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 09:02:52 -1000 [thread overview]
Message-ID: <ZnXOXHOa2NwbTc3i@slm.duckdns.org> (raw)
In-Reply-To: <656fdcee-dc51-4286-899d-aec4b88ab3a0@sirena.org.uk>
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
prev parent reply other threads:[~2024-06-21 19:02 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
2024-06-21 11:09 ` Mark Brown
2024-06-21 19:02 ` Tejun Heo [this message]
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=ZnXOXHOa2NwbTc3i@slm.duckdns.org \
--to=tj@kernel.org \
--cc=broonie@kernel.org \
--cc=dvernet@meta.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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