BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com, davemarchevsky@fb.com
Subject: Re: [PATCH v2 bpf-next 0/3] Revamp and fix libbpf's feature-probing APIs
Date: Fri, 17 Dec 2021 22:20:11 +0000	[thread overview]
Message-ID: <163977961139.17343.116378339550967950.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211217171202.3352835-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Fri, 17 Dec 2021 09:11:59 -0800 you wrote:
> Fix and improve libbpf feature-probing APIs. Name them consistently and
> deprecated previous inconsistently named APIs.
> 
> v1->v2:
>   - fixed misleading comment and added acks (Dave).
> 
> Cc: Dave Marchevsky <davemarchevsky@fb.com>
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/3] libbpf: rework feature-probing APIs
    https://git.kernel.org/bpf/bpf-next/c/878d8def0603
  - [v2,bpf-next,2/3] selftests/bpf: add libbpf feature-probing API selftests
    https://git.kernel.org/bpf/bpf-next/c/5a8ea82f9d25
  - [v2,bpf-next,3/3] bpftool: reimplement large insn size limit feature probing
    https://git.kernel.org/bpf/bpf-next/c/e967a20a8fab

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-12-17 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 17:11 [PATCH v2 bpf-next 0/3] Revamp and fix libbpf's feature-probing APIs Andrii Nakryiko
2021-12-17 17:12 ` [PATCH v2 bpf-next 1/3] libbpf: rework " Andrii Nakryiko
2021-12-17 17:12 ` [PATCH v2 bpf-next 2/3] selftests/bpf: add libbpf feature-probing API selftests Andrii Nakryiko
2021-12-17 17:12 ` [PATCH v2 bpf-next 3/3] bpftool: reimplement large insn size limit feature probing Andrii Nakryiko
2021-12-17 22:20 ` patchwork-bot+netdevbpf [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=163977961139.17343.116378339550967950.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davemarchevsky@fb.com \
    --cc=kernel-team@fb.com \
    /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