From: Yonghong Song <yonghong.song@linux.dev>
To: Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org
Cc: kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/2] selftests/bpf: add uprobe_multi test binary to .gitignore
Date: Wed, 23 Aug 2023 17:42:33 -0700 [thread overview]
Message-ID: <05db092d-6b5d-7e27-ce6a-b4fd022f2d89@linux.dev> (raw)
In-Reply-To: <20230824000016.2658017-1-andrii@kernel.org>
On 8/23/23 5:00 PM, Andrii Nakryiko wrote:
> It seems like it was forgotten to add uprobe_multi binary to .gitignore.
> Fix this trivial omission.
>
> Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
I actually noticed this problem as well. Thanks for the fix!
Acked-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> tools/testing/selftests/bpf/.gitignore | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/bpf/.gitignore b/tools/testing/selftests/bpf/.gitignore
> index 110518ba4804..f1aebabfb017 100644
> --- a/tools/testing/selftests/bpf/.gitignore
> +++ b/tools/testing/selftests/bpf/.gitignore
> @@ -44,6 +44,7 @@ test_cpp
> /bench
> /veristat
> /sign-file
> +/uprobe_multi
> *.ko
> *.tmp
> xskxceiver
next prev parent reply other threads:[~2023-08-24 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 0:00 [PATCH bpf-next 1/2] selftests/bpf: add uprobe_multi test binary to .gitignore Andrii Nakryiko
2023-08-24 0:00 ` [PATCH bpf-next 2/2] libbpf: fix signedness determination in CO-RE relo handling logic Andrii Nakryiko
2023-08-24 0:43 ` Yonghong Song
2023-08-24 0:42 ` Yonghong Song [this message]
2023-08-24 4:50 ` [PATCH bpf-next 1/2] selftests/bpf: add uprobe_multi test binary to .gitignore patchwork-bot+netdevbpf
2023-08-24 13:07 ` Jiri Olsa
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=05db092d-6b5d-7e27-ce6a-b4fd022f2d89@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
/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