linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hindborg <a.hindborg@kernel.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-block@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] Rust in FS, Storage, MM
Date: Fri, 14 Feb 2025 07:41:03 +0100	[thread overview]
Message-ID: <87ldu9uiyo.fsf@kernel.org> (raw)

Hi All,

On behalf of the Linux kernel Rust subsystem team, I would like to suggest a
general plenary session focused on Rust. Based on audience interest we would
discuss:

 - Status of rust adoption in each subsystem - what did we achieve since last
   LSF?
 - Insights from the maintainers of subsystems that have merged Rust - how was
   the experience?
 - A reflection on process - does the current approach work or should we change
   something?
 - General Q&A

Please note that unfortunately I will be the only representative from the Rust
subsystem team on site this year.

Best regards,
Andreas Hindborg



             reply	other threads:[~2025-02-14  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14  6:41 Andreas Hindborg [this message]
2025-02-15  0:18 ` Steve French
2025-02-17 10:41 ` Gao Xiang

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=87ldu9uiyo.fsf@kernel.org \
    --to=a.hindborg@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=rust-for-linux@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