From: patchwork-bot+linux-riscv@kernel.org
To: Mi@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Dapeng <dapeng1.mi@linux.intel.com>
Cc: linux-riscv@lists.infradead.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, john.g.garry@oracle.com,
will@kernel.org, james.clark@linaro.org, mike.leach@linaro.org,
guoren@kernel.org, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
linux-kernel@vger.kernel.org, zide.chen@intel.com,
thomas.falcon@intel.com, dapeng1.mi@intel.com,
xudong.hao@intel.com
Subject: Re: [Patch v3 0/4] Perf tools: perf-regs bug fix and optimization
Date: Tue, 24 Mar 2026 06:07:31 +0000 [thread overview]
Message-ID: <177433245177.469836.2784785880641063798.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203024356.444942-1-dapeng1.mi@linux.intel.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Arnaldo Carvalho de Melo <acme@redhat.com>:
On Tue, 3 Feb 2026 10:43:52 +0800 you wrote:
> Changes:
> v2 -> v3:
> * Fix the abort issue for "-I" or "--user-regs" options. (Patch 1/4)
> * Address Ian's comments.
>
> v1 -> v2:
> * Fixing "PERF_REG_EXTENDED_MASK" redefinition building error by
> changing the "asm/perf_regs.h" header path to relative UAPI path.
> (Patch 1/3)
> * Spliting xxx_reg_mask() and xxx_sdt_arg_parse_op() conversion into 2
> patches.
>
> [...]
Here is the summary with links:
- [v3,1/4] perf regs: Fix abort for "-I" or "--user-regs" options
https://git.kernel.org/riscv/c/c2e28ae2946f
- [v3,2/4] perf arch: Update arch headers to use relative UAPI paths
https://git.kernel.org/riscv/c/e716e69cf67b
- [v3,3/4] perf regs: Remove __weak attributive arch__xxx_reg_mask() functions
(no matching commit)
- [v3,4/4] perf regs: Remove __weak attributive arch_sdt_arg_parse_op() function
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-24 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 2:43 [Patch v3 0/4] Perf tools: perf-regs bug fix and optimization Dapeng Mi
2026-02-03 2:43 ` [Patch v3 1/4] perf regs: Fix abort for "-I" or "--user-regs" options Dapeng Mi
2026-02-03 23:06 ` Ian Rogers
2026-02-03 2:43 ` [Patch v3 2/4] perf arch: Update arch headers to use relative UAPI paths Dapeng Mi
2026-02-03 2:43 ` [Patch v3 3/4] perf regs: Remove __weak attributive arch__xxx_reg_mask() functions Dapeng Mi
2026-02-03 23:08 ` Ian Rogers
2026-02-03 2:43 ` [Patch v3 4/4] perf regs: Remove __weak attributive arch_sdt_arg_parse_op() function Dapeng Mi
2026-02-03 23:11 ` Ian Rogers
2026-02-06 15:17 ` [Patch v3 0/4] Perf tools: perf-regs bug fix and optimization Arnaldo Carvalho de Melo
2026-02-09 0:46 ` Mi, Dapeng
2026-03-24 6:07 ` patchwork-bot+linux-riscv [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=177433245177.469836.2784785880641063798.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Mi@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alex@ghiti.fr \
--cc=alexander.shishkin@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=guoren@kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=thomas.falcon@intel.com \
--cc=will@kernel.org \
--cc=xudong.hao@intel.com \
--cc=zide.chen@intel.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