From: Josef Bacik <josef@toxicpanda.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-nvme@vger.kernel.org" <linux-nvme@vger.kernel.org>
Subject: [LSFMMBPF 2021] A status update
Date: Fri, 4 Dec 2020 10:48:53 -0500 [thread overview]
Message-ID: <fd5264ac-c84d-e1d4-01e2-62b9c05af892@toxicpanda.com> (raw)
Hello,
We on the program committee hope everybody has been able to stay safe and
healthy during this challenging time, and look forward to being able to see all
of you in person again when it is safe.
The current plans for LSFMMBPF 2021 are to schedule an in person conference in
H2 (after June) of 2021. The tentative plan is to use the same hotel that we
had planned to use for 2020, as we still have contracts with them. However
clearly that is not set in stone. The Linux Foundation has done a wonderful job
of working with us to formulate a plan and figure out the logistics that will
work the best for everybody, I really can't thank them enough for their help.
Once we have a finalized date we will redo the CFP emails, probably coming out
March time frame. If you have any questions or concerns please feel free to
respond to this email, or email me or any of the other PC members privately and
we will do our best to answer your questions. Rest assured the general timing
of the conference is going to take into account the wide variety of schedules
that we are dealing with, and we will do our best to come up with something that
works for as many as people as possible.
We hope that you and your families continue to stay safe and health. Thank you
on behalf of the program committee:
Josef Bacik (Filesystems)
Amir Goldstein (Filesystems)
Martin K. Petersen (Storage)
Omar Sandoval (Storage)
Michal Hocko (MM)
Dan Williams (MM)
Alexei Starovoitov (BPF)
Daniel Borkmann (BPF)
next reply other threads:[~2020-12-04 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 15:48 Josef Bacik [this message]
2020-12-12 17:29 ` [LSFMMBPF 2021] A status update Matthew Wilcox
2020-12-15 12:23 ` Michal Hocko
2020-12-15 13:43 ` Hannes Reinecke
2021-01-05 20:30 ` Joao Martins
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=fd5264ac-c84d-e1d4-01e2-62b9c05af892@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=bpf@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-xfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).