From: Christoph Hellwig <hch@lst.de>
To: ast@kernel.org, daniel@iogearbox.net
Cc: bpf@vger.kernel.org
Subject: LSF/MM session: eBPF standardization
Date: Tue, 3 May 2022 16:04:49 +0200 [thread overview]
Message-ID: <20220503140449.GA22470@lst.de> (raw)
Hi Alexei and Daniel,
if you have some time left I'd like to kick off a short discussion on
what to do about documenting and standardizing eBPF.
next reply other threads:[~2022-05-03 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:04 Christoph Hellwig [this message]
2022-05-10 8:16 ` LSF/MM session: eBPF standardization Christoph Hellwig
2022-05-12 2:39 ` Alexei Starovoitov
2022-05-17 9:10 ` Christoph Hellwig
2022-05-17 22:29 ` Harris, James R
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=20220503140449.GA22470@lst.de \
--to=hch@lst.de \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.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