From: patchwork-bot+netdevbpf@kernel•org
To: Juhee Kang <claudiajkang@gmail•com>
Cc: daniel@iogearbox•net, ast@kernel•org, andrii@kernel•org,
yhs@fb•com, netdev@vger•kernel.org, bpf@vger•kernel.org
Subject: Re: [bpf-next v2 1/2] samples: bpf: Fix tracex7 error raised on the missing argument
Date: Tue, 27 Jul 2021 18:20:05 +0000 [thread overview]
Message-ID: <162741000593.4520.5117531432819411073.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210727041056.23455-1-claudiajkang@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Tue, 27 Jul 2021 04:10:55 +0000 you wrote:
> The current behavior of 'tracex7' doesn't consist with other bpf samples
> tracex{1..6}. Other samples do not require any argument to run with, but
> tracex7 should be run with btrfs device argument. (it should be executed
> with test_override_return.sh)
>
> Currently, tracex7 doesn't have any description about how to run this
> program and raises an unexpected error. And this result might be
> confusing since users might not have a hunch about how to run this
> program.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] samples: bpf: Fix tracex7 error raised on the missing argument
https://git.kernel.org/bpf/bpf-next/c/7d07006f0592
- [bpf-next,v2,2/2] samples: bpf: Add the omitted xdp samples to .gitignore
https://git.kernel.org/bpf/bpf-next/c/05e9b4f60d31
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-27 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 4:10 [bpf-next v2 1/2] samples: bpf: Fix tracex7 error raised on the missing argument Juhee Kang
2021-07-27 4:10 ` [bpf-next v2 2/2] samples: bpf: Add the omitted xdp samples to .gitignore Juhee Kang
2021-07-27 18:20 ` 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=162741000593.4520.5117531432819411073.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=claudiajkang@gmail$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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