From: Christian Brauner <brauner@kernel.org>
To: Haris Iqbal <haris.iqbal@ionos.com>
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, lwn@lwn.net
Subject: Re: LSF/MM/BPF: 2026: Call for Proposals
Date: Wed, 18 Feb 2026 10:56:42 +0100 [thread overview]
Message-ID: <20260218-haben-protokollieren-d4b5d2a1f8c9@brauner> (raw)
In-Reply-To: <CAJpMwyg-3-Z=ZDC60Vn0s-8Z78VOPKYmvX9s=Nnvcoao4T5zbg@mail.gmail.com>
On Tue, Feb 17, 2026 at 11:37:19AM +0100, Haris Iqbal wrote:
> On Mon, Feb 16, 2026 at 3:28 PM Christian Brauner <brauner@kernel.org> wrote:
> >
> > On Thu, Jan 29, 2026 at 05:13:52PM +0100, Christian Brauner wrote:
> > > On Mon, Jan 19, 2026 at 03:26:39PM +0100, Christian Brauner wrote:
> > > > > (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.
> >
> > This is (likely) the final reminder to put in your invitation request!
> > The invitation request form closes this Friday, 20th February.
>
> Hello,
>
> What is the announcement date for accepted topics and invitations?
We will very likely aim to get the initial batch of invitations out the
middle or end of February.
next prev parent reply other threads:[~2026-02-18 9:56 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 [this message]
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=20260218-haben-protokollieren-d4b5d2a1f8c9@brauner \
--to=brauner@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=haris.iqbal@ionos.com \
--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