BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pengcheng Yang <yangpc@wangsu.com>
Cc: quentin@isovalent.com, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, song@kernel.org, sdf@google.com,
	bpf@vger.kernel.org
Subject: Re: [PATCH v2 bpf-next] bpftool: Support bpffs mountpoint as pin path for prog loadall
Date: Wed, 17 May 2023 14:10:19 +0000	[thread overview]
Message-ID: <168433261962.10644.15924445827364561434.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1683342439-3677-1-git-send-email-yangpc@wangsu.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Sat,  6 May 2023 11:07:19 +0800 you wrote:
> Currently, when using prog loadall, if the pin path is a bpffs
> mountpoint, bpffs will be repeatedly mounted to the parent directory
> of the bpffs mountpoint path.
> 
> For example,
>     $ bpftool prog loadall test.o /sys/fs/bpf
> currently bpffs will be repeatedly mounted to /sys/fs.
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next] bpftool: Support bpffs mountpoint as pin path for prog loadall
    https://git.kernel.org/bpf/bpf-next/c/2a36c26fe3b8

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



      parent reply	other threads:[~2023-05-17 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06  3:07 [PATCH v2 bpf-next] bpftool: Support bpffs mountpoint as pin path for prog loadall Pengcheng Yang
2023-05-09  8:18 ` Quentin Monnet
2023-05-17 14:10 ` 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=168433261962.10644.15924445827364561434.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=quentin@isovalent.com \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=yangpc@wangsu.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