BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dmitrii Dolgov <9erthalion6@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, quentin@isovalent.com, yhs@fb.com
Subject: Re: [PATCH bpf-next v6] bpftool: Add bpf_cookie to link output
Date: Tue, 15 Mar 2022 22:10:09 +0000	[thread overview]
Message-ID: <164738220972.10122.15428582260020075303.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220309163112.24141-1-9erthalion6@gmail.com>

Hello:

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

On Wed,  9 Mar 2022 17:31:12 +0100 you wrote:
> Commit 82e6b1eee6a8 ("bpf: Allow to specify user-provided bpf_cookie for
> BPF perf links") introduced the concept of user specified bpf_cookie,
> which could be accessed by BPF programs using bpf_get_attach_cookie().
> For troubleshooting purposes it is convenient to expose bpf_cookie via
> bpftool as well, so there is no need to meddle with the target BPF
> program itself.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6] bpftool: Add bpf_cookie to link output
    https://git.kernel.org/bpf/bpf-next/c/cbdaf71f7e65

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-03-15 22:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 16:31 [PATCH bpf-next v6] bpftool: Add bpf_cookie to link output Dmitrii Dolgov
2022-03-11 22:24 ` Andrii Nakryiko
2022-03-12 22:59   ` Quentin Monnet
2022-03-15 18:33     ` Andrii Nakryiko
2022-03-15 21:01       ` Quentin Monnet
2022-03-15 22:10 ` patchwork-bot+netdevbpf [this message]
2022-03-26  1:38 ` Quentin Monnet
2022-03-26  9:08   ` Dmitry Dolgov
2022-03-27 22:03     ` Quentin Monnet
2022-03-28 13:06       ` Dmitry Dolgov
2022-03-28 21:39       ` Andrii Nakryiko

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=164738220972.10122.15428582260020075303.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=9erthalion6@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=quentin@isovalent.com \
    --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