From: Daniel Borkmann <daniel@iogearbox.net>
To: Jiri Olsa <olsajiri@gmail.com>, Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH bpf-next] tools headers: Remove s390 ptrace.h in check-headers.sh
Date: Tue, 11 Apr 2023 19:35:02 +0200 [thread overview]
Message-ID: <0f77e29c-e384-1d67-a99c-91e6091ec7db@iogearbox.net> (raw)
In-Reply-To: <ZC/wA2NoO7yI/xNm@krava>
On 4/7/23 12:27 PM, Jiri Olsa wrote:
> On Fri, Apr 07, 2023 at 10:21:30AM +0800, Tiezhu Yang wrote:
>> After commit 1f265d2aea0d ("selftests/bpf: Remove not used headers"),
>> tools/arch/s390/include/uapi/asm/ptrace.h has been removed, so remove
>> it in check-headers.sh too, otherwise we can see the following build
>> warning:
>>
>> diff: tools/arch/s390/include/uapi/asm/ptrace.h: No such file or directory
>>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Link: https://lore.kernel.org/oe-kbuild-all/202304050029.38NdbQPf-lkp@intel.com/
>> Fixes: 1f265d2aea0d ("selftests/bpf: Remove not used headers")
>> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
>
> not sure this should go through Arnaldo's tree instead,
> either way is fine with me
Agree, perf tree is better given the script is located there, so:
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
next prev parent reply other threads:[~2023-04-11 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 2:21 [PATCH bpf-next] tools headers: Remove s390 ptrace.h in check-headers.sh Tiezhu Yang
2023-04-07 10:27 ` Jiri Olsa
2023-04-11 17:35 ` Daniel Borkmann [this message]
2023-04-12 13:33 ` Arnaldo Carvalho de Melo
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=0f77e29c-e384-1d67-a99c-91e6091ec7db@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=acme@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=olsajiri@gmail.com \
--cc=yangtiezhu@loongson.cn \
/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).