From: Steven Rostedt <rostedt@goodmis.org>
To: Chris Li <chrisl@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>,
YoungJun Park <youngjun.park@lge.com>,
ksummit@lists.linux.dev, gunho.lee@lge.com, taejoon.song@lge.com,
linux-mm@kvack.org, David Hildenbrand <david@redhat.com>
Subject: Re: [TECH TOPIC] Per-cgroup Swap Device Control
Date: Fri, 22 Aug 2025 14:26:50 -0400 [thread overview]
Message-ID: <20250822142650.572507ff@gandalf.local.home> (raw)
In-Reply-To: <CACePvbUYp7w68C8z_TeMhOJQ0hmWw1jkwy+D_Lb+N5WbmufAug@mail.gmail.com>
On Fri, 22 Aug 2025 11:13:41 -0700
Chris Li <chrisl@kernel.org> wrote:
> Anyway, is there any conflict to apply to LPC MM Micro Conference
> track as well? Of course which conference to apply to is a decision
> for YoungJun to make. I am just curious what options are available
> now.
Note that MC topics are more discussion focused than either the Refereed or
Kernel Summit tracks. A MC topic is between 15 to 30 minutes which does not
give much time for presentations. A Track topic is longer and allows more
presentation of the topic. Also, acceptance to a Track talk gives a pass to
Plumbers, whereas acceptance to an MC topic does not guarantee one.
>
> Hi, YoungJun,
>
> If you decide to apply for LPC MM MC track as well, don't forget to
> register yourself as a speaker on the LPC website.
> https://lpc.events/event/19/abstracts/
> The lower right of the page, there is a button "Submit a new abstract",
> Click on that to start the process. Don't forget to select the pull
> down menu MM Micro conference.
The part I left out of Ted's email was:
Secondly, please create a topic at the Linux Plumbers Conference
proposal submission site and target it to the Kernel Summit track:
https://lpc.events/event/19/abstracts
Please do both steps. I'll try to notice if someone forgets one or the
other, but your chances of making sure your proposal gets the necessary
attention and consideration are maximized by submitting both to the
mailing list and the web site.
So YoungJun has already signed up to the website and proposed a Kernel
Summit track. It can be switched over to a MM MC topic by editing the
submitted abstract and switch the Track over to:
"Kernel Memory Management MC"
-- Steve
next prev parent reply other threads:[~2025-08-22 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aKgm+wisMipLqnL4@yjaykim-PowerEdge-T330>
2025-08-22 16:58 ` Matthew Wilcox
2025-08-22 17:10 ` Steven Rostedt
2025-08-22 17:43 ` Matthew Wilcox
2025-08-22 18:13 ` Chris Li
2025-08-22 18:26 ` Steven Rostedt [this message]
2025-08-23 0:42 ` YoungJun Park
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=20250822142650.572507ff@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=gunho.lee@lge.com \
--cc=ksummit@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=taejoon.song@lge.com \
--cc=willy@infradead.org \
--cc=youngjun.park@lge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox