BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Delyan Kratunov <delyank@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net
Subject: Re: [PATCH bpf-next] libbpf: deprecate priv/set_priv storage
Date: Thu, 03 Feb 2022 20:40:09 +0000	[thread overview]
Message-ID: <164392080971.19679.12302322534218675117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220203180032.1921580-1-delyank@fb.com>

Hello:

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

On Thu, 3 Feb 2022 10:00:32 -0800 you wrote:
> Arbitrary storage via bpf_*__set_priv/__priv is being deprecated
> without a replacement ([1]). perf uses this capability, but most of
> that is going away with the removal of prologue generation ([2]).
> perf is already suppressing deprecation warnings, so the remaining
> cleanup will happen separately.
> 
>   [1]: Closes: https://github.com/libbpf/libbpf/issues/294
>   [2]: https://lore.kernel.org/bpf/20220123221932.537060-1-jolsa@kernel.org/
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: deprecate priv/set_priv storage
    https://git.kernel.org/bpf/bpf-next/c/ca33aa4ec5cb

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



      reply	other threads:[~2022-02-03 20:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 18:00 [PATCH bpf-next] libbpf: deprecate priv/set_priv storage Delyan Kratunov
2022-02-03 20:40 ` 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=164392080971.19679.12302322534218675117.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=delyank@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