From: Andrea Righi <arighi@nvidia.com>
To: sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joelagnelf@nvidia.com>,
Daniel Hodges <hodgesd@meta.com>,
Changwoo Min <changwoo@igalia.com>, Tejun Heo <tj@kernel.org>,
David Vernet <void@manifault.com>,
Pat Somaru <patso@likewhatevs.io>,
Patrick Lu <perf.patrick.lu@gmail.com>,
Valentin Andrei <vandrei@meta.com>,
John Stultz <jstultz@google.com>,
Jake Hillion <lpc@jakehillion.me>,
Emil Tsalapatis <sites@etsalapatis.com>,
Aniket Gattani <aniketgattani@google.com>,
David Dai <daidavid1@gmail.com>
Subject: Re: [ANNOUNCEMENT] LPC 2025 sched_ext Microconference CFP
Date: Thu, 4 Dec 2025 14:50:48 +0100 [thread overview]
Message-ID: <aTGRuFmciJzk9iLD@gpd4> (raw)
In-Reply-To: <aJLnn4YbTiNXAnZG@gpd4>
Hi everyone,
with LPC approaching, I'd like to share a few logistic notes and guidelines
for the microconference.
- Check the schedule: the final agenda is available here, if your assigned
slot doesn't work, please let me know and we can try to adjust it:
https://lpc.events/event/19/sessions/229/#20251212
- Session length: each slot is 15 minutes (18 minutes in practice, to
allow smooth speaker transitions).
- Be concise: aim for 1–2 introductory slides to set the context, then
dive directly into the core topic.
- Prioritize interaction: the microconference is discussion-driven, make
sure to leave enough time for Q&A and audience participation.
- Expect interruptions: it's perfectly fine (and actually ideal) if you
don't reach the last slide because questions spark conversation, so make
sure to put your key points at the beginning of the deck.
- Share work-in-progress: talks should not present polished or finalized
work, instead, focus on open issues and opportunities for collaborative
brainstorming around kernel development.
See also:
https://lpc.events/blog/current/index.php/2023/06/26/the-ideal-microconference-topic-session/
Looking forward to seeing you in Tokyo next week!
Thanks,
-Andrea
prev parent reply other threads:[~2025-12-04 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 8:34 [ANNOUNCEMENT] LPC 2025 sched_ext Microconference CFP Andrea Righi
2025-08-06 5:26 ` Andrea Righi
2025-12-04 13:50 ` Andrea Righi [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=aTGRuFmciJzk9iLD@gpd4 \
--to=arighi@nvidia.com \
--cc=aniketgattani@google.com \
--cc=changwoo@igalia.com \
--cc=daidavid1@gmail.com \
--cc=hodgesd@meta.com \
--cc=joelagnelf@nvidia.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lpc@jakehillion.me \
--cc=patso@likewhatevs.io \
--cc=perf.patrick.lu@gmail.com \
--cc=sched-ext@lists.linux.dev \
--cc=sites@etsalapatis.com \
--cc=tj@kernel.org \
--cc=vandrei@meta.com \
--cc=void@manifault.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.