From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: pull-request: bpf 2019-08-11
Date: Sun, 11 Aug 2019 14:49:53 -0700 (PDT) [thread overview]
Message-ID: <20190811.144953.272254761097299399.davem@davemloft.net> (raw)
In-Reply-To: <20190811195834.3430-1-daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Sun, 11 Aug 2019 21:58:34 +0200
> The following pull-request contains BPF updates for your *net* tree.
>
> The main changes are:
>
> 1) x64 JIT code generation fix for backward-jumps to 1st insn, from Alexei.
>
> 2) Fix buggy multi-closing of BTF file descriptor in libbpf, from Andrii.
>
> 3) Fix libbpf_num_possible_cpus() to make it thread safe, from Takshak.
>
> 4) Fix bpftool to dump an error if pinning fails, from Jakub.
>
> Please consider pulling these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Pulled, thanks Daniel.
prev parent reply other threads:[~2019-08-11 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 19:58 pull-request: bpf 2019-08-11 Daniel Borkmann
2019-08-11 21:49 ` David Miller [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=20190811.144953.272254761097299399.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.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).