BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	dsahern@kernel.org, brouer@redhat.com, toke@redhat.com,
	lorenzo.bianconi@redhat.com, andrii@kernel.org,
	john.fastabend@gmail.com
Subject: Re: [PATCH v3 bpf-next 0/3] libbpf: deprecate xdp_cpumap, xdp_devmap and classifier sec definitions
Date: Tue, 01 Feb 2022 18:00:10 +0000	[thread overview]
Message-ID: <164373841092.21178.15446692367658403571.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1643727185.git.lorenzo@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Tue,  1 Feb 2022 15:58:07 +0100 you wrote:
> Deprecate xdp_cpumap, xdp_devmap and classifier sec definitions.
> Update cpumap/devmap samples and kselftests.
> 
> Changes since v2:
> - update warning log
> - split libbpf and samples/kselftests changes
> - deprecate classifier sec definition
> 
> [...]

Here is the summary with links:
  - [v3,bpf-next,1/3] libbpf: deprecate xdp_cpumap, xdp_devmap and classifier sec definitions
    https://git.kernel.org/bpf/bpf-next/c/4a4d4cee48e2
  - [v3,bpf-next,2/3] selftests/bpf: update cpumap/devmap sec_name
    https://git.kernel.org/bpf/bpf-next/c/439f0336566c
  - [v3,bpf-next,3/3] samples/bpf: update cpumap/devmap sec_name
    https://git.kernel.org/bpf/bpf-next/c/8bab53223340

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-02-01 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 14:58 [PATCH v3 bpf-next 0/3] libbpf: deprecate xdp_cpumap, xdp_devmap and classifier sec definitions Lorenzo Bianconi
2022-02-01 14:58 ` [PATCH v3 bpf-next 1/3] " Lorenzo Bianconi
2022-02-01 14:58 ` [PATCH v3 bpf-next 2/3] selftests/bpf: update cpumap/devmap sec_name Lorenzo Bianconi
2022-02-01 14:58 ` [PATCH v3 bpf-next 3/3] samples/bpf: " Lorenzo Bianconi
2022-02-01 18:00 ` 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=164373841092.21178.15446692367658403571.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=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=dsahern@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lorenzo@kernel.org \
    --cc=toke@redhat.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