From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <mrpre@163.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev, ast@kernel.org,
edumazet@google.com, jakub@cloudflare.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
linux-kernel@vger.kernel.org, song@kernel.org,
john.fastabend@gmail.com, andrii@kernel.org, mhal@rbox.co,
yonghong.song@linux.dev, daniel@iogearbox.net,
xiyou.wangcong@gmail.com, horms@kernel.org, eddyz87@gmail.com,
mykolal@fb.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
pulehui@huawei.com
Subject: Re: [PATCH bpf-next v2] selftests/bpf: avoid generating untracked files when running bpf selftests
Date: Mon, 06 Jan 2025 14:10:30 +0000 [thread overview]
Message-ID: <173617263051.3505180.15711457709343352794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241224075957.288018-1-mrpre@163.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 24 Dec 2024 15:59:57 +0800 you wrote:
> Currently, when we run the BPF selftests with the following command:
> 'make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS=""'
>
> The command generates untracked files and directories with make version
> less than 4.4:
> '''
> Untracked files:
> (use "git add <file>..." to include in what will be committed)
> tools/testing/selftests/bpfFEATURE-DUMP.selftests
> tools/testing/selftests/bpffeature/
> '''
> We lost slash after word "bpf".
>
> [...]
Here is the summary with links:
- [bpf-next,v2] selftests/bpf: avoid generating untracked files when running bpf selftests
https://git.kernel.org/bpf/bpf-next/c/73b9075f334f
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:[~2025-01-06 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 7:59 [PATCH bpf-next v2] selftests/bpf: avoid generating untracked files when running bpf selftests Jiayuan Chen
2024-12-29 21:40 ` Jiri Olsa
2025-01-06 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=173617263051.3505180.15711457709343352794.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=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--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=mhal@rbox.co \
--cc=mrpre@163.com \
--cc=mykolal@fb.com \
--cc=pabeni@redhat.com \
--cc=pulehui@huawei.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=xiyou.wangcong@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox