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,
lwn@lwn.net
Subject: Re: LSF/MM/BPF: 2026: Call for Proposals
Date: Mon, 19 Jan 2026 15:26:39 +0100 [thread overview]
Message-ID: <20260119-bagger-desaster-e11c27458c49@brauner> (raw)
In-Reply-To: <20260110-lsfmm-2026-cfp-ae970765d60e@brauner>
> (1) Fill out the following Google form to request attendance and
> suggest any topics for discussion:
>
> https://forms.gle/hUgiEksr8CA1migCA
>
> If advance notice is required for visa applications, please point
> that out in your proposal or request to attend, and submit the topic
> as soon as possible.
Hey everyone,
This is a reminder to put in your invitation request for LSF/MM/BPF 2026!
The sooner you do this the easier it is for us to plan and the less time
we have to spend hunting down missing attendees just weeks prior to the
event. Unless you're really hankering for the special-snowflake
experience please do your part and get in your invitation request.
Please also don't forget to pester^wask^wremind your respective
organizations to consider sponsoring LSF/MM/BPF 2026.
Thanks!
Christian
next prev parent reply other threads:[~2026-01-19 14:26 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 [this message]
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
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=20260119-bagger-desaster-e11c27458c49@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=lwn@lwn.net \
/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