From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: damon@lists.linux.dev, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [CFP] DAMON Nanoconference (aka BoF) at LPC'26
Date: Sat, 8 Aug 2026 09:27:24 -0700 [thread overview]
Message-ID: <20260808162724.92408-1-sj@kernel.org> (raw)
In-Reply-To: <20260806003357.92659-1-sj@kernel.org>
On Wed, 5 Aug 2026 17:33:57 -0700 SJ Park <sj@kernel.org> wrote:
> Hello community,
>
>
> We will have a DAMON BoF session [1] at LPC'26. Because it is a BoF, I want to
> make it as casual as possible with many voices. Hence inviting you. You could
> think this as yet another version of our bi-weekly Beer/Coffee/Tea chat meeting
> series [2], or the first Nano-sized DAMON conference.
>
> If you have any topics about DAMON that you want to present and discuss in the
> session, please send an email to me.
>
> Example of topics include but not limited to:
>
> - Your DAMON work that is recently landed, in progress/plan
> - Your DAMON usage and success/failure stories
>
> Depending on the topic and number of proposals, I will try to give each topic
> 5-15 minutes.
We already got plenty number of proposals. I'm closing the CFP. Sorry for not
announcing an official proposal deadline in advance. Please feel free to send
any DAMON topic, though. We could extend the session to hallway track, evening
event or a later DAMON Beer/Coffee/Tea chat. Also that will be helpful for
planning the next DAMON Conference.
>
>
> [1] https://lpc.events/event/20/contributions/2453/
> [2] https://docs.google.com/document/d/1v43Kcj3ly4CYqmAkMaZzLiM2GEnWfgdGbZAH3mi2vpM/edit?usp=sharing
Thanks,
SJ
prev parent reply other threads:[~2026-08-08 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 0:33 [CFP] DAMON Nanoconference (aka BoF) at LPC'26 SJ Park
2026-08-08 16:27 ` SJ Park [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=20260808162724.92408-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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