linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: <dan.j.williams@intel.com>
To: <linux-cxl@vger.kernel.org>, <linux-mm@kvack.org>,
	<linux-rdma@vger.kernel.org>, <dri-devel@lists.freedesktop.org>
Cc: <linux-kernel@vger.kernel.org>, <a.manzanares@samsung.com>
Subject: CFP: Plumbers 2025: Device Memory (formerly CXL) Microconference
Date: Wed, 30 Jul 2025 15:22:37 -0700	[thread overview]
Message-ID: <688a9b2d35c97_48e5100af@dwillia2-xfh.jf.intel.com.notmuch> (raw)

Hello,

Linux Plumbers 2025, to be held December 11th through the 13th in Tokyo
[1], will host the "Device and Specific Purpose Memory Microconference".
Topic submissions are now being accepted.

Go to:

https://lpc.events/event/19/abstracts/

...and use the "Submit New Abstract" button. Select "Device and Specific
Purpose Memory MC" to submit a topic proposal. Some topic suggestions
are listed in the abstract for the track [2], and here is some general
guidance for uConf submissions [3].

Plumbers Registration opens: September 14th 2025. Submit your proposal
by September 7th if you want to be considered in the first wave of
acceptance notifications. Topics will be considered on a rolling basis
until the end of September, or if the schedule fills up before then.

Looking forward to the discussions, see you there!

[1]: https://events.linuxfoundation.org/open-source-summit-japan/attend/venue-travel/
[2]: https://lpc.events/event/19/abstracts/2204/
[3]: https://lpc.events/blog/current/index.php/2023/06/26/the-ideal-microconference-topic-session/


             reply	other threads:[~2025-07-30 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30 22:22 dan.j.williams [this message]
2025-07-31  3:14 ` CFP: Plumbers 2025: Device Memory (formerly CXL) Microconference dan.j.williams

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=688a9b2d35c97_48e5100af@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=a.manzanares@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rdma@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).