From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Martin Lau <kafai@fb.com>
Cc: Andrii Nakryiko <andriin@fb.com>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@fb.com>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"andrii.nakryiko@gmail.com" <andrii.nakryiko@gmail.com>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [Potential Spoof] [PATCH v2 bpf-next 0/2] selftests/bpf Makefile cleanup and fixes
Date: Sat, 12 Oct 2019 16:22:49 -0700 [thread overview]
Message-ID: <CAADnVQJ-__rn88Z1wgPsRdGdtyznG_rO3=kCx+7rSSENUE-dyw@mail.gmail.com> (raw)
In-Reply-To: <20191012071526.lgrzyvyhnyvzh7ao@kafai-mbp.dhcp.thefacebook.com>
On Sat, Oct 12, 2019 at 12:25 AM Martin Lau <kafai@fb.com> wrote:
>
> On Fri, Oct 11, 2019 at 03:01:44PM -0700, Andrii Nakryiko wrote:
> > Patch #1 enforces libbpf build to have bpf_helper_defs.h ready before test BPF
> > programs are built.
> > Patch #2 drops obsolete BTF/pahole detection logic from Makefile.
> Acked-by: Martin KaFai Lau <kafai@fb.com>
Applied. Thanks
prev parent reply other threads:[~2019-10-12 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 22:01 [PATCH v2 bpf-next 0/2] selftests/bpf Makefile cleanup and fixes Andrii Nakryiko
2019-10-11 22:01 ` [PATCH v2 bpf-next 1/2] selftests/bpf: enforce libbpf build before BPF programs are built Andrii Nakryiko
2019-10-11 22:01 ` [PATCH v2 bpf-next 2/2] selftests/bpf: remove obsolete pahole/BTF support detection Andrii Nakryiko
2019-10-12 7:15 ` [Potential Spoof] [PATCH v2 bpf-next 0/2] selftests/bpf Makefile cleanup and fixes Martin Lau
2019-10-12 23:22 ` Alexei Starovoitov [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='CAADnVQJ-__rn88Z1wgPsRdGdtyznG_rO3=kCx+7rSSENUE-dyw@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=Kernel-team@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).