[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ca5d8ed-c0ad-af21-fc84-eb64b02dc20f@huawei.com>
Date: Wed, 22 Nov 2023 09:02:08 +0800
From: Yang Jihong <yangjihong1@...wei.com>
To: Namhyung Kim <namhyung@...nel.org>
CC: <peterz@...radead.org>, <mingo@...hat.com>, <acme@...nel.org>,
<mark.rutland@....com>, <alexander.shishkin@...ux.intel.com>,
<jolsa@...nel.org>, <irogers@...gle.com>,
<adrian.hunter@...el.com>, <avagin@...gle.com>,
<daniel.diaz@...aro.org>, <linux-perf-users@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] perf bench sched-seccomp-notify: Fix __NR_seccomp
undeclared build error on i386
Hello,
On 2023/11/22 2:57, Namhyung Kim wrote:
> Hello,
>
> On Fri, Nov 17, 2023 at 6:51 PM Yang Jihong <yangjihong1@...wei.com> wrote:
>>
>> Fix a build error on i386 system:
>>
>> bench/sched-seccomp-notify.c: In function 'seccomp':
>> bench/sched-seccomp-notify.c:46:17: error: '__NR_seccomp' undeclared (first use in this function); did you mean 'seccomp'?
>> return syscall(__NR_seccomp, op, flags, args);
>> ^~~~~~~~~~~~
>> seccomp
>> bench/sched-seccomp-notify.c:46:17: note: each undeclared identifier is reported only once for each function it appears in
>> bench/sched-seccomp-notify.c:47:1: error: control reaches end of non-void function [-Werror=return-type]
>> }
>> ^
>> cc1: all warnings being treated as errors
>>
>> Fixes: 7d5cb68af638 ("perf/benchmark: add a new benchmark for seccom_unotify")
>> Signed-off-by: Yang Jihong <yangjihong1@...wei.com>
>
> This is already fixed by:
> https://lore.kernel.org/all/20231017083019.31733-1-jirislaby@kernel.org/
>
I didn't notice this patch... okay, please ignore it.
Thanks,
Yang
Powered by blists - more mailing lists