From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
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: Fri, 23 Jan 2026 11:16:17 +0100 [thread overview]
Message-ID: <20260123-tapir-perspektive-e6466483739a@brauner> (raw)
In-Reply-To: <20260122032209.GE3183987@ZenIV>
On Thu, Jan 22, 2026 at 03:22:09AM +0000, Al Viro wrote:
> 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?
I did already have you in mind as a remote attendee and we will have a
solution for such cases. But we do not provide a general first-class
"virtual experience" as some tracks do not even want any remote
attendeeds.
TL;DR you're good.
prev parent reply other threads:[~2026-01-23 10:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 13:24 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-01-22 3:22 ` Al Viro
2026-01-23 10:16 ` Christian Brauner [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=20260123-tapir-perspektive-e6466483739a@brauner \
--to=brauner@kernel.org \
--cc=bpf@vger.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 \
--cc=viro@zeniv.linux.org.uk \
/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