netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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-next 2019-05-06
Date: Tue, 07 May 2019 09:29:32 -0700 (PDT)	[thread overview]
Message-ID: <20190507.092932.293198732805725041.davem@davemloft.net> (raw)
In-Reply-To: <20190506151822.19628-1-daniel@iogearbox.net>

From: Daniel Borkmann <daniel@iogearbox.net>
Date: Mon,  6 May 2019 17:18:22 +0200

> The following pull-request contains BPF updates for your *net-next* tree.
> 
> The main changes are:
> 
> 1) Two AF_XDP libbpf fixes for socket teardown; first one an invalid
>    munmap and the other one an invalid skmap cleanup, both from Björn.
> 
> 2) More graceful CONFIG_DEBUG_INFO_BTF handling when pahole is not
>    present in the system to generate vmlinux btf info, from Andrii.
> 
> 3) Fix libbpf and thus fix perf build error with uClibc on arc
>    architecture, from Vineet.
> 
> 4) Fix missing libbpf_util.h header install in libbpf, from William.
> 
> 5) Exclude bash-completion/bpftool from .gitignore pattern, from Masahiro.
> 
> 6) Fix up rlimit in test_libbpf_open kselftest test case, from Yonghong.
> 
> 7) Minor misc cleanups.
> 
> Please consider pulling these changes from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git

Pulled, thanks.

      reply	other threads:[~2019-05-07 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 15:18 pull-request: bpf-next 2019-05-06 Daniel Borkmann
2019-05-07 16:29 ` 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=20190507.092932.293198732805725041.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).