From: Christian Brauner <brauner@kernel.org>
To: 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
Cc: lsf-pc@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: LSF/MM/BPF: 2026: (V)FS: Second Round of Invites Sent
Date: Mon, 16 Mar 2026 11:20:39 +0100 [thread overview]
Message-ID: <20260316-gebiss-drehkreuz-1f3f0e7a96df@brauner> (raw)
In-Reply-To: <20260225-aufeinander-kummervoll-1953a06beae9@brauner>
On Wed, Feb 25, 2026 at 03:52:23PM +0100, Christian Brauner wrote:
> Hey everyone,
>
> I sent out the first round of invites for the (V)FS track.
> The first batch is also the largest batch. We will send out a set of
> smaller invites later.
Hey everyone,
I sent out the second and last batch of invites for the (V)FS track.
I've also sent out declined invitation notices. In case you have
received neither it is to be treated as a declined invitation at this
point.
Should any attendees be unable to attend because of... events... we may
be able to notify people on the list but it will likely be very short
notice unfortunately.
Thanks!
Christian
prev parent reply other threads:[~2026-03-16 10:20 UTC|newest]
Thread overview: 13+ 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
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 ` 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=20260316-gebiss-drehkreuz-1f3f0e7a96df@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 \
/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