All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tao Chen <chen.dylane@linux.dev>
Cc: qmo@kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
	song@kernel.org, yonghong.song@linux.dev,
	john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
	haoluo@google.com, jolsa@kernel.org, davem@davemloft.net,
	kuba@kernel.org, hawk@kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 1/3] bpftool: Add bpf_token show
Date: Sat, 02 Aug 2025 01:15:14 +0000	[thread overview]
Message-ID: <175409731401.4179816.14714600690863735034.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250723144442.1427943-1-chen.dylane@linux.dev>

Hello:

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

On Wed, 23 Jul 2025 22:44:40 +0800 you wrote:
> Add `bpftool token show` command to get token info
> from bpffs in /proc/mounts.
> 
> Example plain output for `token show`:
> token_info  /sys/fs/bpf/token
> 	allowed_cmds:
> 	  map_create          prog_load
> 	allowed_maps:
> 	allowed_progs:
> 	  kprobe
> 	allowed_attachs:
> 	  xdp
> token_info  /sys/fs/bpf/token2
> 	allowed_cmds:
> 	  map_create          prog_load
> 	allowed_maps:
> 	allowed_progs:
> 	  kprobe
> 	allowed_attachs:
> 	  xdp
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/3] bpftool: Add bpf_token show
    https://git.kernel.org/bpf/bpf-next/c/2d812311c2b2
  - [bpf-next,v4,2/3] bpftool: Add bpftool-token manpage
    https://git.kernel.org/bpf/bpf-next/c/b7f640084916
  - [bpf-next,v4,3/3] bpftool: Add bash completion for token argument
    https://git.kernel.org/bpf/bpf-next/c/f3af62b6cee8

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



  parent reply	other threads:[~2025-08-02  1:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 14:44 [PATCH bpf-next v4 1/3] bpftool: Add bpf_token show Tao Chen
2025-07-23 14:44 ` [PATCH bpf-next v4 2/3] bpftool: Add bpftool-token manpage Tao Chen
2025-07-23 14:44 ` [PATCH bpf-next v4 3/3] bpftool: Add bash completion for token argument Tao Chen
2025-07-28 15:25 ` [PATCH bpf-next v4 1/3] bpftool: Add bpf_token show Tao Chen
2025-07-29  2:34   ` Alexei Starovoitov
2025-08-02  1:15 ` patchwork-bot+netdevbpf [this message]
     [not found] ` <20250913162643.879707-1-clm@meta.com>
2025-09-15 16:21   ` Andrii Nakryiko
2025-09-16  2:16     ` Tao Chen

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=175409731401.4179816.14714600690863735034.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=chen.dylane@linux.dev \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=qmo@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.