BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sahid Orentino Ferdjaoui  <sahid.ferdjaoui@industrialdiscipline.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, quentin@isovalent.com, yhs@fb.com,
	martin.lau@linux.dev, song@kernel.org, john.fastabend@gmail.com,
	kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
	jolsa@kernel.org
Subject: Re: [PATCH bpf-next v4 0/5] clean-up bpftool from legacy support
Date: Mon, 21 Nov 2022 00:30:19 +0000	[thread overview]
Message-ID: <166899061947.20533.8436347774688840570.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221120112515.38165-1-sahid.ferdjaoui@industrialdiscipline.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Sun, 20 Nov 2022 11:25:46 +0000 you wrote:
> As part of commit 93b8952d223a ("libbpf: deprecate legacy BPF map
> definitions") and commit bd054102a8c7 ("libbpf: enforce strict libbpf
> 1.0 behaviors") The --legacy option is not relevant anymore. #1 is
> removing it. #4 is cleaning the code from using libbpf_get_error().
> 
> About patches #2 and #3 They are changes discovered while working on
> this series (credits to Quentin Monnet). #2 is cleaning-up usage of an
> unnecessary PTR_ERR(NULL), finally #3 is fixing an invalid value
> passed to strerror().
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/5] bpftool: remove support of --legacy option for bpftool
    https://git.kernel.org/bpf/bpf-next/c/9b8107553424
  - [bpf-next,v4,2/5] bpftool: replace return value PTR_ERR(NULL) with 0
    https://git.kernel.org/bpf/bpf-next/c/989f285159b8
  - [bpf-next,v4,3/5] bpftool: fix error message when function can't register struct_ops
    https://git.kernel.org/bpf/bpf-next/c/d2973ffd25c2
  - [bpf-next,v4,4/5] bpftool: clean-up usage of libbpf_get_error()
    https://git.kernel.org/bpf/bpf-next/c/d1313e01271d
  - [bpf-next,v4,5/5] bpftool: remove function free_btf_vmlinux()
    https://git.kernel.org/bpf/bpf-next/c/52df1a8aabad

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



  parent reply	other threads:[~2022-11-21  0:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 11:25 [PATCH bpf-next v4 0/5] clean-up bpftool from legacy support Sahid Orentino Ferdjaoui
2022-11-20 11:25 ` [PATCH bpf-next v4 1/5] bpftool: remove support of --legacy option for bpftool Sahid Orentino Ferdjaoui
2022-11-20 11:26 ` [PATCH bpf-next v4 2/5] bpftool: replace return value PTR_ERR(NULL) with 0 Sahid Orentino Ferdjaoui
2022-11-20 15:35 ` [PATCH bpf-next v4 0/5] clean-up bpftool from legacy support Quentin Monnet
2022-11-21  0:30 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-20 11:13 Sahid Orentino Ferdjaoui

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=166899061947.20533.8436347774688840570.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=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=quentin@isovalent.com \
    --cc=sahid.ferdjaoui@industrialdiscipline.com \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=yhs@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