From: Daniel Borkmann <email@example.com> To: firstname.lastname@example.org, email@example.com Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: LPC 2021 Networking and BPF Track CFP Date: Tue, 6 Apr 2021 17:27:50 +0200 Message-ID: <email@example.com> (raw) We are pleased to announce the Call for Proposals (CFP) for the Networking and BPF track at the 2021 edition of the Linux Plumbers Conference (LPC), which is planned to be held in Dublin, Ireland, on September 27th - 29th, 2021. Note that if an in-person conference should prove to be impossible due to the circumstances at that time, Linux Plumbers will switch to a virtual-only conference. CFP submitters should ideally be able to give their presentation in person, if circumstances permit, although presenting remotely will always be possible. This year's Networking and BPF track technical committee is comprised of: David S. Miller <firstname.lastname@example.org> Jakub Kicinski <email@example.com> Eric Dumazet <firstname.lastname@example.org> Alexei Starovoitov <email@example.com> Daniel Borkmann <firstname.lastname@example.org> Andrii Nakryiko <email@example.com> 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.
next reply index Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-06 15:27 Daniel Borkmann [this message] 2021-07-06 19:33 ` LPC 2021 Networking and BPF Track CFP (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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
BPF Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/bpf/0 bpf/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 bpf bpf/ https://lore.kernel.org/bpf \ email@example.com public-inbox-index bpf Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.bpf AGPL code for this site: git clone https://public-inbox.org/public-inbox.git