From: Huacai Chen <chenhuacai@kernel.org>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: acme@kernel.org, mingo@redhat.com, peterz@infradead.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, namhyung@kernel.org, irogers@google.com,
adrian.hunter@intel.com, linux-perf-users@vger.kernel.org,
loongson-kernel@lists.loongnix.cn, loongarch@lists.linux.dev
Subject: Re: [PATCH v1 0/2] tools/perf: Add loongarch cpuinfo and fix build warning
Date: Tue, 22 Aug 2023 23:10:58 +0800 [thread overview]
Message-ID: <CAAhV-H4pCdHn63c9N5oL39ja2ZPB9+v37D7exhaoW3m+FsPL7w@mail.gmail.com> (raw)
In-Reply-To: <cover.1692694595.git.siyanteng@loongson.cn>
For this series:
Acked-by: Huacai Chen <chenhuacai@loongson.cn>
On Tue, Aug 22, 2023 at 5:32 PM Yanteng Si <siyanteng@loongson.cn> wrote:
>
> * LoongArch and riscv don't have tools/arch/xxxxx/include/uapi/asm/mman.h,
> let's modify the detection rules.
> * Allow to use cpuinfo on loongarch.
>
> Yanteng Si (2):
> perf/trace: Fix mmap_flags for archs use generic mman.h
> perf/tools: Allow to use cpuinfo on loongarch
>
> tools/perf/trace/beauty/mmap_flags.sh | 2 +-
> tools/perf/util/header.c | 2 ++
> tools/perf/util/svghelper.c | 7 ++++++-
> 3 files changed, 9 insertions(+), 2 deletions(-)
>
> --
> 2.31.4
>
>
prev parent reply other threads:[~2023-08-22 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 9:32 [PATCH v1 0/2] tools/perf: Add loongarch cpuinfo and fix build warning Yanteng Si
2023-08-22 9:32 ` [PATCH v1 1/2] perf/trace: Fix mmap_flags for archs use generic mman.h Yanteng Si
2023-08-22 18:02 ` Arnaldo Carvalho de Melo
2023-08-23 7:11 ` Yanteng Si
2023-08-23 11:36 ` Arnaldo Carvalho de Melo
2023-08-24 2:22 ` Yanteng Si
2023-08-24 13:33 ` Arnaldo Carvalho de Melo
2023-08-22 9:32 ` [PATCH v1 2/2] perf/tools: Allow to use cpuinfo on loongarch Yanteng Si
2023-08-22 17:50 ` Arnaldo Carvalho de Melo
2023-08-23 7:11 ` Yanteng Si
2023-08-22 15:10 ` Huacai Chen [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=CAAhV-H4pCdHn63c9N5oL39ja2ZPB9+v37D7exhaoW3m+FsPL7w@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=siyanteng@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).