linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: xdp-newbies@vger.kernel.org, iovisor-dev@lists.iovisor.org,
	linux-wireless@vger.kernel.org, netfilter-devel@vger.kernel.org,
	lwn@lwn.net
Subject: LPC 2021 Networking and BPF Track CFP (Reminder)
Date: Tue, 6 Jul 2021 21:33:03 +0200	[thread overview]
Message-ID: <c549da28-a3c0-9478-4b91-7aa2ff124b69@iogearbox.net> (raw)
In-Reply-To: <6d225920-9ecc-ef24-2bf8-848ca86c7fb0@iogearbox.net>

This is a reminder for the Call for Proposals (CFP) for the Networking and
BPF track at the 2021 edition of the Linux Plumbers Conference (LPC), which
will be held virtually on the wider Internet, on September 20th - 24th, 2021.

This year's Networking and BPF track technical committee is comprised of:

   David S. Miller <davem@davemloft.net>
   Jakub Kicinski <kuba@kernel.org>
   Eric Dumazet <edumazet@google.com>
   Alexei Starovoitov <ast@kernel.org>
   Daniel Borkmann <daniel@iogearbox.net>
   Andrii Nakryiko <andrii@kernel.org>

We are seeking proposals of 40 minutes in length (including Q&A discussion),
optionally accompanied by papers of 2 to 10 pages in length.

Any kind of advanced Linux networking and/or BPF related topic will be considered.

Please submit your proposals through the official LPC website at:

   https://linuxplumbersconf.org/event/11/abstracts/

Make sure to select "Networking & BPF Summit" in the Track pull-down menu.

Proposals must be submitted by August 13th, and submitters will be notified of
acceptance by August 16th.

Final slides and papers (as PDF) are due on the first day of the conference.

  reply	other threads:[~2021-07-06 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 15:27 LPC 2021 Networking and BPF Track CFP Daniel Borkmann
2021-07-06 19:33 ` Daniel Borkmann [this message]
2021-08-06 19:50   ` LPC 2021 Networking and BPF Track CFP (2nd reminder) Daniel Borkmann

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=c549da28-a3c0-9478-4b91-7aa2ff124b69@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=bpf@vger.kernel.org \
    --cc=iovisor-dev@lists.iovisor.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=xdp-newbies@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).