From: Dave Thaler <dthaler@microsoft.com>
To: "bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Followup from LSF/MM/BPF on standardization/documentation
Date: Mon, 8 Aug 2022 18:54:13 +0000 [thread overview]
Message-ID: <CH2PR21MB14647EC978225E98A3B8AD73A3639@CH2PR21MB1464.namprd21.prod.outlook.com> (raw)
In-Reply-To: <fa09a9f1-7d99-cafb-3c10-7a3e474d8da6@iogearbox.net>
At LSF/MM/BPF, the topic was raised about better documenting eBPF and making "standards" like documentation, especially since we are having runtimes other than just Linux now supporting eBPF. And ideally hosting it under the eBPF Foundation.
I'd like to use this week's BPF office hours slot (Thursday 9am Pacific) to kick off a discussion of this topic, so wanted to send this email to invite anyone interested in contributing to such an effort. Hopefully we can discuss how to organize the effort and some principles we might use for what might be in scope.
Dave
next prev parent reply other threads:[~2022-08-08 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 20:59 LPC 2022 Networking and BPF Track CFP Daniel Borkmann
2022-07-14 21:19 ` LPC 2022 Networking and BPF Track CFP (Reminder) Daniel Borkmann
2022-08-04 16:52 ` LPC 2022 Networking and BPF Track CFP (Final Reminder) Daniel Borkmann
2022-08-08 18:54 ` Dave Thaler [this message]
2022-08-11 17:23 ` Followup from LSF/MM/BPF on standardization/documentation Dave Thaler
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=CH2PR21MB14647EC978225E98A3B8AD73A3639@CH2PR21MB1464.namprd21.prod.outlook.com \
--to=dthaler@microsoft.com \
--cc=bpf@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).