From: Namhyung Kim <namhyung@kernel.org>
To: Yang Jihong <yangjihong1@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
avagin@google.com, daniel.diaz@linaro.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] A few fixes for i386 build errors
Date: Mon, 20 Nov 2023 21:24:39 -0800 [thread overview]
Message-ID: <CAM9d7cgGWKj1T6-cjntHvMDgTkVKzNQFPWW8BxQwRKChJdpniw@mail.gmail.com> (raw)
In-Reply-To: <20231118024858.1567039-1-yangjihong1@huawei.com>
Hello,
On Fri, Nov 17, 2023 at 6:51 PM Yang Jihong <yangjihong1@huawei.com> wrote:
>
> Yang Jihong (3):
> perf kwork: Fix a build error on 32-bit
> perf lock contention: Fix a build error on 32-bit
> perf bench sched-seccomp-notify: Fix __NR_seccomp undeclared build
> error on i386
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks for the fix!
Namhyung
>
> tools/arch/x86/include/uapi/asm/unistd_32.h | 2 +-
> tools/perf/builtin-kwork.c | 2 +-
> tools/perf/util/bpf_lock_contention.c | 3 ++-
> 3 files changed, 4 insertions(+), 3 deletions(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-11-21 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 2:48 [PATCH 0/3] A few fixes for i386 build errors Yang Jihong
2023-11-18 2:48 ` [PATCH 1/3] perf kwork: Fix a build error on 32-bit Yang Jihong
2023-11-18 2:48 ` [PATCH 2/3] perf lock contention: " Yang Jihong
2023-11-18 2:48 ` [PATCH 3/3] perf bench sched-seccomp-notify: Fix __NR_seccomp undeclared build error on i386 Yang Jihong
2023-11-21 18:57 ` Namhyung Kim
2023-11-22 1:02 ` Yang Jihong
2023-11-21 5:24 ` Namhyung Kim [this message]
2023-11-22 19:24 ` [PATCH 0/3] A few fixes for i386 build errors Namhyung Kim
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=CAM9d7cgGWKj1T6-cjntHvMDgTkVKzNQFPWW8BxQwRKChJdpniw@mail.gmail.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=avagin@google.com \
--cc=daniel.diaz@linaro.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yangjihong1@huawei.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;
as well as URLs for NNTP newsgroup(s).