From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, ast@kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: pull-request: bpf-next 2020-12-14
Date: Mon, 14 Dec 2020 18:10:39 -0800 [thread overview]
Message-ID: <20201214181039.2b58ef46@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20201214214316.20642-1-daniel@iogearbox.net>
On Mon, 14 Dec 2020 22:43:16 +0100 Daniel Borkmann wrote:
> 1) Expose bpf_sk_storage_*() helpers to iterator programs, from Florent Revest.
>
> 2) Add AF_XDP selftests based on veth devs to BPF selftests, from Weqaar Janjua.
>
> 3) Support for finding BTF based kernel attach targets through libbpf's
> bpf_program__set_attach_target() API, from Andrii Nakryiko.
>
> 4) Permit pointers on stack for helper calls in the verifier, from Yonghong Song.
>
> 5) Fix overflows in hash map elem size after rlimit removal, from Eric Dumazet.
>
> 6) Get rid of direct invocation of llc in BPF selftests, from Andrew Delgadillo.
>
> 7) Fix xsk_recvmsg() to reorder socket state check before access, from Björn Töpel.
>
> 8) Add new libbpf API helper to retrieve ring buffer epoll fd, from Brendan Jackman.
>
> 9) Batch of minor BPF selftest improvements all over the place, from Florian Lehner,
> KP Singh, Jiri Olsa and various others.
Looks like the reply bot is not keeping it 100.. I'll report
to Konstantin after the merge window craziness is over.
Pulled, thanks!
prev parent reply other threads:[~2020-12-15 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 21:43 pull-request: bpf-next 2020-12-14 Daniel Borkmann
2020-12-15 2:10 ` Jakub Kicinski [this message]
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=20201214181039.2b58ef46@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--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).