The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Martin Kaiser <martin@kaiser.cx>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] perf: riscv: fix register name strings
Date: Wed, 10 Jun 2026 16:55:25 -0300	[thread overview]
Message-ID: <ainBLXCDcudjqBl2@x1> (raw)
In-Reply-To: <20260609081500.743861-1-martin@kaiser.cx>

On Tue, Jun 09, 2026 at 10:13:07AM +0200, Martin Kaiser wrote:
> Fix the register name strings for risc-v to match the syntax for kprobes.
> 
> This requires redefining REG_DWARFNUM_NAME. Make sure that different
> definitions for different architectures don't create compiler warnings.

Thanks, applied to perf-tools-next, for v7.2.

- Arnaldo
 
> Martin Kaiser (2):
>   perf: avoid redefinition warnings for REG_DWARFNUM_NAME
>   perf riscv: fix register name strings
> 
>  tools/perf/arch/powerpc/include/dwarf-regs-table.h | 1 +
>  tools/perf/arch/riscv/include/dwarf-regs-table.h   | 3 ++-
>  tools/perf/arch/s390/include/dwarf-regs-table.h    | 1 +
>  3 files changed, 4 insertions(+), 1 deletion(-)
> 
> -- 
> 2.43.7

      parent reply	other threads:[~2026-06-10 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09  8:13 [PATCH v2 0/2] perf: riscv: fix register name strings Martin Kaiser
2026-06-09  8:13 ` [PATCH v2 1/2] perf: avoid redefinition warnings for REG_DWARFNUM_NAME Martin Kaiser
2026-06-09  8:13 ` [PATCH v2 2/2] perf riscv: fix register name strings Martin Kaiser
2026-06-10 19:55 ` Arnaldo Carvalho de Melo [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=ainBLXCDcudjqBl2@x1 \
    --to=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=martin@kaiser.cx \
    --cc=namhyung@kernel.org \
    /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