From: Al Viro <viro@zeniv.linux.org.uk>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
bpf@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: LSF/MM/BPF: 2026: Call for Proposals
Date: Thu, 22 Jan 2026 03:22:09 +0000 [thread overview]
Message-ID: <20260122032209.GE3183987@ZenIV> (raw)
In-Reply-To: <20260110-lsfmm-2026-cfp-ae970765d60e@brauner>
On Sat, Jan 10, 2026 at 02:24:17PM +0100, Christian Brauner wrote:
> The annual Linux Storage, Filesystem, Memory Management, and BPF
> (LSF/MM/BPF) Summit for 2026 will be held May 4–6, 2026 in Zagreb,
> Croatia.
>
> LSF/MM/BPF is an invitation-only technical workshop to map out
> improvements to the Linux storage, filesystem, BPF, and memory
> management subsystems that will make their way into the mainline
> kernel within the coming years.
>
> LSF/MM/BPF 2026 will be a three-day, stand-alone conference with four
> subsystem-specific tracks, cross-track discussions, as well as BoF and
> hacking sessions.
Will there be an option for remote participation this year?
next prev parent reply other threads:[~2026-01-22 3:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 13:24 LSF/MM/BPF: 2026: Call for Proposals Christian Brauner
2026-01-19 14:26 ` Christian Brauner
2026-01-29 16:13 ` Christian Brauner
2026-02-16 14:25 ` Christian Brauner
2026-02-17 10:37 ` Haris Iqbal
2026-02-18 9:56 ` Christian Brauner
2026-02-24 9:53 ` Christian Brauner
2026-02-24 13:37 ` James Bottomley
2026-02-26 2:52 ` John Hubbard
2026-01-22 3:22 ` Al Viro [this message]
2026-01-23 10:16 ` Christian Brauner
2026-02-25 14:52 ` LSF/MM/BPF: 2026: (V)FS: First Round of Invites Sent Christian Brauner
2026-03-16 10:20 ` LSF/MM/BPF: 2026: (V)FS: Second " Christian Brauner
2026-04-22 20:29 ` LSF/MM/BPF: 2026: Call for Proposals Bart Van Assche
2026-04-22 21:28 ` Roman Gushchin
2026-04-23 11:46 ` Christian Brauner
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=20260122032209.GE3183987@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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 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.