From: Jiong Wang <jiong.wang@netronome.com>
To: alexei.starovoitov@gmail.com, daniel@iogearbox.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
Jiong Wang <jiong.wang@netronome.com>
Subject: [PATCH bpf-next v2 1/4] selftests: bpf: add "alu32" to .gitignore
Date: Mon, 11 Feb 2019 12:01:18 +0000 [thread overview]
Message-ID: <1549886481-25848-2-git-send-email-jiong.wang@netronome.com> (raw)
In-Reply-To: <1549886481-25848-1-git-send-email-jiong.wang@netronome.com>
"alu32" is a build dir and contains various files for BPF sub-register
code-gen testing.
This patch tells git to ignore it.
Suggested-by: Yonghong Song <yhs@fb.com>
Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: Jiong Wang <jiong.wang@netronome.com>
---
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 dd093bd..e47168d 100644
--- a/tools/testing/selftests/bpf/.gitignore
+++ b/tools/testing/selftests/bpf/.gitignore
@@ -29,3 +29,4 @@ test_netcnt
test_section_names
test_tcpnotify_user
test_libbpf
+alu32
--
2.7.4
next prev parent reply other threads:[~2019-02-11 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 12:01 [PATCH bpf-next v2 0/4] selftests: bpf: improve bpf object file rules Jiong Wang
2019-02-11 12:01 ` Jiong Wang [this message]
2019-02-11 12:01 ` [PATCH bpf-next v2 2/4] selftests: bpf: extend sub-register mode compilation to all bpf object files Jiong Wang
2019-02-11 12:01 ` [PATCH bpf-next v2 3/4] selftests: bpf: centre kernel bpf objects under new subdir "progs" Jiong Wang
2019-02-11 12:01 ` [PATCH bpf-next v2 4/4] selftests: bpf: relax sub-register mode compilation criteria Jiong Wang
2019-02-12 4:34 ` [PATCH bpf-next v2 0/4] selftests: bpf: improve bpf object file rules Alexei Starovoitov
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=1549886481-25848-2-git-send-email-jiong.wang@netronome.com \
--to=jiong.wang@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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