netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org, netfilter-devel@vger.kernel.org,
	bpf@vger.kernel.org, xdp-newbies@vger.kernel.org, lwn@lwn.net
Subject: LPC 2020 Networking and BPF Track CFP (Reminder)
Date: Wed, 22 Jul 2020 15:48:20 -0700 (PDT)	[thread overview]
Message-ID: <20200722.154820.1749937838006185071.davem@davemloft.net> (raw)


[ The deadline is a week and a half away, please get your submissions
  in soon! ]

This is a reminder for the call for proposals for the networking and
bpf track at the Linux Plumbers Conference on the wider internet,
which will be happening on August 24th-28th, 2020.

This year the technical committee is comprised of:

David S. Miller <davem@davemloft.net>
Alexei Starovoitov <ast@kernel.org>
Daniel Borkmann <daniel@iogearbox.net>
Jakub Sitnicki <jakub@cloudflare.com>
Paolo Abeni <pabeni@redhat.com>
Jakub Kicinski <kuba@kernel.org>
Michal Kubecek <mkubecek@suse.cz>
Sabrina Dubroca <sd@queasysnail.net>

We are seeking talks of 40 minutes in length (including Q & A),
optionally accompanied by papers of 2 to 10 pages in length.  The
papers, while not required, are very strongly encouraged by the
committee.  The submitters intention to provide a paper will be taken
into consideration as a criteria when deciding which proposals to
accept.

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

Please submit your proposals on the LPC website at:

	https://www.linuxplumbersconf.org/event/7/abstracts/#submit-abstract

And be sure to select "Networking & BPF Summit" in the Track
pulldown menu.

Proposals must be submitted by August 2nd, and submitters will be
notified of acceptance by August 9th.

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

                 reply	other threads:[~2020-07-22 22:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200722.154820.1749937838006185071.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bpf@vger.kernel.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).