From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: bpf <bpf@vger.kernel.org>, Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
Network Development <netdev@vger.kernel.org>
Subject: bpf-next is OPEN
Date: Fri, 17 Apr 2020 10:42:18 -0700 [thread overview]
Message-ID: <CAADnVQKaRPsSp6CptpLVyv=QoXnkvnU6NxYWZ=faA9pxYJ5YQA@mail.gmail.com> (raw)
Looking at RFCs for bpf-next this release cycle is going to be exciting! :)
next reply other threads:[~2020-04-17 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 17:42 Alexei Starovoitov [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-18 8:38 bpf-next is OPEN Daniel Borkmann
2020-06-17 15:10 Alexei Starovoitov
2019-09-30 20:51 Daniel Borkmann
2019-07-22 23:57 Daniel Borkmann
2019-05-21 22:25 Daniel Borkmann
2019-03-19 8:52 Daniel Borkmann
2019-03-19 17:01 ` Alban Crequy
2019-03-19 21:11 ` 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='CAADnVQKaRPsSp6CptpLVyv=QoXnkvnU6NxYWZ=faA9pxYJ5YQA@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@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).