From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-perf-users@vger.kernel.org, loongarch@lists.linux.dev
Subject: Re: [PATCH RESEND v3 0/5] perf tools: Modify mksyscalltbl
Date: Mon, 5 Jun 2023 11:44:11 -0300 [thread overview]
Message-ID: <ZH30uwj7S72vxoX1@kernel.org> (raw)
In-Reply-To: <CAP-5=fXvN1b+_krmFSL2=C31WZ3zKafnq=Bqw3ruBKFNzG_8Kw@mail.gmail.com>
Em Tue, May 30, 2023 at 12:03:30PM -0700, Ian Rogers escreveu:
> On Tue, May 30, 2023 at 3:10 AM Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
> >
> > I'm sorry, somehow the patchset didn't reach mailing lists.
> > Resending with a fewer people in the cc list, which probably
> > was the reason.
> >
> > Thanks Alexander, Leo and Ian for your reviews and suggestions.
>
> Thanks for the consts!
>
> Acked-by: Ian Rogers <irogers@google.com>
Thanks, applied.
- Arnaldo
> > v3:
> > -- Add a new patch to declare syscalltbl_*[] as const for all archs,
> > suggested by Ian.
> > -- Add a new patch to use max_nr to define SYSCALLTBL_ARM64_MAX_ID.
> >
> > v2:
> > -- Add a new patch to rename create_table_from_c()
> > to create_sc_table(), suggested by Leo.
> > -- Simplify the shell script, suggested by Alexander.
> >
> > Tiezhu Yang (5):
> > perf tools: Declare syscalltbl_*[] as const for all archs
> > perf arm64: Rename create_table_from_c() to create_sc_table()
> > perf arm64: Handle __NR3264_ prefixed syscall number
> > perf arm64: Use max_nr to define SYSCALLTBL_ARM64_MAX_ID
> > perf LoongArch: Simplify mksyscalltbl
> >
> > tools/perf/arch/arm64/entry/syscalls/mksyscalltbl | 17 ++++-----
> > .../arch/loongarch/entry/syscalls/mksyscalltbl | 40 +++++++---------------
> > tools/perf/arch/mips/entry/syscalls/mksyscalltbl | 2 +-
> > .../perf/arch/powerpc/entry/syscalls/mksyscalltbl | 2 +-
> > tools/perf/arch/s390/entry/syscalls/mksyscalltbl | 2 +-
> > tools/perf/arch/x86/entry/syscalls/syscalltbl.sh | 2 +-
> > tools/perf/util/syscalltbl.c | 14 ++++----
> > 7 files changed, 32 insertions(+), 47 deletions(-)
> >
> > --
> > 2.1.0
> >
--
- Arnaldo
next prev parent reply other threads:[~2023-06-05 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 10:09 [PATCH RESEND v3 0/5] perf tools: Modify mksyscalltbl Tiezhu Yang
2023-05-30 10:09 ` [PATCH RESEND v3 1/5] perf tools: Declare syscalltbl_*[] as const for all archs Tiezhu Yang
2023-05-30 10:09 ` [PATCH RESEND v3 2/5] perf arm64: Rename create_table_from_c() to create_sc_table() Tiezhu Yang
2023-05-30 10:09 ` [PATCH RESEND v3 3/5] perf arm64: Handle __NR3264_ prefixed syscall number Tiezhu Yang
2023-05-30 10:10 ` [PATCH RESEND v3 4/5] perf arm64: Use max_nr to define SYSCALLTBL_ARM64_MAX_ID Tiezhu Yang
2023-05-30 10:10 ` [PATCH RESEND v3 5/5] perf LoongArch: Simplify mksyscalltbl Tiezhu Yang
2023-05-30 19:03 ` [PATCH RESEND v3 0/5] perf tools: Modify mksyscalltbl Ian Rogers
2023-06-05 14:44 ` Arnaldo Carvalho de Melo [this message]
2023-05-31 7:58 ` Huacai Chen
2023-06-05 14:44 ` 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=ZH30uwj7S72vxoX1@kernel.org \
--to=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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