From: David Vernet <void@manifault.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, bsegall@google.com, bristot@redhat.com,
vschneid@redhat.com, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@kernel.org, joshdon@google.com, brho@google.com,
pjt@google.com, derkling@google.com, haoluo@google.com,
youssefesmat@google.com, greg.marsden@oracle.com,
willy@infradead.org, andrea.righi@canonical.com,
andrealmeid@igalia.com, changwoo@igalia.com, gpiccoli@igalia.com,
tj@kernel.org, colin.i.king@gmail.com, ast@kernel.org,
julia.lawall@inria.fr, himadrispandya@gmail.com,
redha.gouicem@rwth-aachen.de, admin@ptr1337.dev,
lucjan.lucjanov@gmail.com
Subject: Re: Sched Ext slack channel / office hours
Date: Mon, 23 Oct 2023 16:43:04 -0500 [thread overview]
Message-ID: <20231023214304.GD32029@maniforge> (raw)
In-Reply-To: <20231023144603.1e18b8bf@gandalf.local.home>
On Mon, Oct 23, 2023 at 02:46:03PM -0400, Steven Rostedt wrote:
> On Mon, 23 Oct 2023 12:53:26 -0500
> David Vernet <void@manifault.com> wrote:
>
> > Yes, it could be beneficial to attend your meeting as well. Please feel
> > free to send us an invitation to any instance of your meeting that is
> > related to sched_ext.
>
> It's a very informal meeting and the agenda is usually created at the
> meeting. So there will never be a "we are going to talk about sched_ext".
Got it.
> If that topic comes up, it will be because the people there want to talk
> about it. The people that usually attend are:
>
> Myself
> Juri Lelli
> Daniel Bristot
> Joel Fernandes
> Vineeth Pillai
> Youssef Esmat
>
> But it's open to anyone that wants to attend. I should send out more
> invites to others that participate in the scheduler work. I sent an invite
> to Peter, but he's never accepted.
>
> And sometimes we get a few others. It's mostly just to discuss latest
> trends of the scheduler.
Sounds good, please send me an invitation and I'll join whenever I'm
available.
Thanks,
David
next prev parent reply other threads:[~2023-10-23 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 20:54 Sched Ext slack channel / office hours David Vernet
2023-10-19 13:31 ` Steven Rostedt
2023-10-23 17:53 ` David Vernet
2023-10-23 18:46 ` Steven Rostedt
2023-10-23 21:43 ` David Vernet [this message]
2023-10-29 7:09 ` Julia Lawall
2023-10-30 14:06 ` David Vernet
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=20231023214304.GD32029@maniforge \
--to=void@manifault.com \
--cc=admin@ptr1337.dev \
--cc=andrea.righi@canonical.com \
--cc=andrealmeid@igalia.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=brho@google.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=colin.i.king@gmail.com \
--cc=daniel@iogearbox.net \
--cc=derkling@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gpiccoli@igalia.com \
--cc=greg.marsden@oracle.com \
--cc=haoluo@google.com \
--cc=himadrispandya@gmail.com \
--cc=joshdon@google.com \
--cc=julia.lawall@inria.fr \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucjan.lucjanov@gmail.com \
--cc=martin.lau@kernel.org \
--cc=pjt@google.com \
--cc=redha.gouicem@rwth-aachen.de \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=willy@infradead.org \
--cc=youssefesmat@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.