From: Stanislav Fomichev <sdf@fomichev.me>
To: Kelsey Skunberg <skunberg.kelsey@gmail.com>
Cc: shuah@kernel.org, ast@kernel.org, daniel@iogearbox.net,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] selftests: bpf: Add files generated when compiled to .gitignore
Date: Sat, 11 May 2019 23:29:07 -0700 [thread overview]
Message-ID: <20190512062907.GL1247@mini-arch> (raw)
In-Reply-To: <20190512035009.25451-1-skunberg.kelsey@gmail.com>
On 05/11, Kelsey Skunberg wrote:
> The following files are generated when /selftests/bpf/ is compiled and
> should be added to .gitignore:
>
> - libbpf.pc
> - libbpf.so.0
> - libbpf.so.0.0.3
>
> Signed-off-by: Kelsey Skunberg <skunberg.kelsey@gmail.com>
> ---
> tools/testing/selftests/bpf/.gitignore | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/.gitignore b/tools/testing/selftests/bpf/.gitignore
> index 41e8a689aa77..ceb11f98fe4f 100644
> --- a/tools/testing/selftests/bpf/.gitignore
> +++ b/tools/testing/selftests/bpf/.gitignore
> @@ -32,3 +32,6 @@ test_tcpnotify_user
> test_libbpf
> test_tcp_check_syncookie_user
> alu32
> +libbpf.pc
[..]
> +libbpf.so.0
> +libbpf.so.0.0.3
How about libbpf.so.* so we don't have to update it on every release?
> --
> 2.20.1
>
WARNING: multiple messages have this Message-ID (diff)
From: sdf at fomichev.me (Stanislav Fomichev)
Subject: [Linux-kernel-mentees] [PATCH] selftests: bpf: Add files generated when compiled to .gitignore
Date: Sat, 11 May 2019 23:29:07 -0700 [thread overview]
Message-ID: <20190512062907.GL1247@mini-arch> (raw)
In-Reply-To: <20190512035009.25451-1-skunberg.kelsey@gmail.com>
On 05/11, Kelsey Skunberg wrote:
> The following files are generated when /selftests/bpf/ is compiled and
> should be added to .gitignore:
>
> - libbpf.pc
> - libbpf.so.0
> - libbpf.so.0.0.3
>
> Signed-off-by: Kelsey Skunberg <skunberg.kelsey at gmail.com>
> ---
> tools/testing/selftests/bpf/.gitignore | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/.gitignore b/tools/testing/selftests/bpf/.gitignore
> index 41e8a689aa77..ceb11f98fe4f 100644
> --- a/tools/testing/selftests/bpf/.gitignore
> +++ b/tools/testing/selftests/bpf/.gitignore
> @@ -32,3 +32,6 @@ test_tcpnotify_user
> test_libbpf
> test_tcp_check_syncookie_user
> alu32
> +libbpf.pc
[..]
> +libbpf.so.0
> +libbpf.so.0.0.3
How about libbpf.so.* so we don't have to update it on every release?
> --
> 2.20.1
>
WARNING: multiple messages have this Message-ID (diff)
From: sdf@fomichev.me (Stanislav Fomichev)
Subject: [Linux-kernel-mentees] [PATCH] selftests: bpf: Add files generated when compiled to .gitignore
Date: Sat, 11 May 2019 23:29:07 -0700 [thread overview]
Message-ID: <20190512062907.GL1247@mini-arch> (raw)
Message-ID: <20190512062907.E-avv61hV2DRP2BaVdGklDzVNF07u1O72b54jm-tCNY@z> (raw)
In-Reply-To: <20190512035009.25451-1-skunberg.kelsey@gmail.com>
On 05/11, Kelsey Skunberg wrote:
> The following files are generated when /selftests/bpf/ is compiled and
> should be added to .gitignore:
>
> - libbpf.pc
> - libbpf.so.0
> - libbpf.so.0.0.3
>
> Signed-off-by: Kelsey Skunberg <skunberg.kelsey at gmail.com>
> ---
> tools/testing/selftests/bpf/.gitignore | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/.gitignore b/tools/testing/selftests/bpf/.gitignore
> index 41e8a689aa77..ceb11f98fe4f 100644
> --- a/tools/testing/selftests/bpf/.gitignore
> +++ b/tools/testing/selftests/bpf/.gitignore
> @@ -32,3 +32,6 @@ test_tcpnotify_user
> test_libbpf
> test_tcp_check_syncookie_user
> alu32
> +libbpf.pc
[..]
> +libbpf.so.0
> +libbpf.so.0.0.3
How about libbpf.so.* so we don't have to update it on every release?
> --
> 2.20.1
>
WARNING: multiple messages have this Message-ID (diff)
From: sdf at fomichev.me (Stanislav Fomichev)
Subject: [PATCH] selftests: bpf: Add files generated when compiled to .gitignore
Date: Sat, 11 May 2019 23:29:07 -0700 [thread overview]
Message-ID: <20190512062907.GL1247@mini-arch> (raw)
In-Reply-To: <20190512035009.25451-1-skunberg.kelsey@gmail.com>
On 05/11, Kelsey Skunberg wrote:
> The following files are generated when /selftests/bpf/ is compiled and
> should be added to .gitignore:
>
> - libbpf.pc
> - libbpf.so.0
> - libbpf.so.0.0.3
>
> Signed-off-by: Kelsey Skunberg <skunberg.kelsey at gmail.com>
> ---
> tools/testing/selftests/bpf/.gitignore | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/.gitignore b/tools/testing/selftests/bpf/.gitignore
> index 41e8a689aa77..ceb11f98fe4f 100644
> --- a/tools/testing/selftests/bpf/.gitignore
> +++ b/tools/testing/selftests/bpf/.gitignore
> @@ -32,3 +32,6 @@ test_tcpnotify_user
> test_libbpf
> test_tcp_check_syncookie_user
> alu32
> +libbpf.pc
[..]
> +libbpf.so.0
> +libbpf.so.0.0.3
How about libbpf.so.* so we don't have to update it on every release?
> --
> 2.20.1
>
WARNING: multiple messages have this Message-ID (diff)
From: sdf@fomichev.me (Stanislav Fomichev)
Subject: [PATCH] selftests: bpf: Add files generated when compiled to .gitignore
Date: Sat, 11 May 2019 23:29:07 -0700 [thread overview]
Message-ID: <20190512062907.GL1247@mini-arch> (raw)
Message-ID: <20190512062907.A5ylX86QXPMmBa1iGldcqUXye07aEgEpKWSYX3AjnZI@z> (raw)
In-Reply-To: <20190512035009.25451-1-skunberg.kelsey@gmail.com>
On 05/11, Kelsey Skunberg wrote:
> The following files are generated when /selftests/bpf/ is compiled and
> should be added to .gitignore:
>
> - libbpf.pc
> - libbpf.so.0
> - libbpf.so.0.0.3
>
> Signed-off-by: Kelsey Skunberg <skunberg.kelsey at gmail.com>
> ---
> tools/testing/selftests/bpf/.gitignore | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/testing/selftests/bpf/.gitignore b/tools/testing/selftests/bpf/.gitignore
> index 41e8a689aa77..ceb11f98fe4f 100644
> --- a/tools/testing/selftests/bpf/.gitignore
> +++ b/tools/testing/selftests/bpf/.gitignore
> @@ -32,3 +32,6 @@ test_tcpnotify_user
> test_libbpf
> test_tcp_check_syncookie_user
> alu32
> +libbpf.pc
[..]
> +libbpf.so.0
> +libbpf.so.0.0.3
How about libbpf.so.* so we don't have to update it on every release?
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-05-12 6:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 3:50 [PATCH] selftests: bpf: Add files generated when compiled to .gitignore Kelsey Skunberg
2019-05-12 3:50 ` Kelsey Skunberg
2019-05-12 3:50 ` skunberg.kelsey
2019-05-12 3:50 ` [Linux-kernel-mentees] " Kelsey Skunberg
2019-05-12 3:50 ` skunberg.kelsey
2019-05-12 6:29 ` Stanislav Fomichev [this message]
2019-05-12 6:29 ` Stanislav Fomichev
2019-05-12 6:29 ` sdf
2019-05-12 6:29 ` [Linux-kernel-mentees] " Stanislav Fomichev
2019-05-12 6:29 ` sdf
2019-05-12 7:34 ` Kelsey Skunberg
2019-05-12 7:34 ` Kelsey Skunberg
2019-05-12 7:34 ` skunberg.kelsey
2019-05-12 7:34 ` [Linux-kernel-mentees] " Kelsey Skunberg
2019-05-12 7:34 ` skunberg.kelsey
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=20190512062907.GL1247@mini-arch \
--to=sdf@fomichev.me \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=skunberg.kelsey@gmail.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.