From: patchwork-bot+linux-riscv@kernel.org
To: Ian Rogers <irogers@google.com>
Cc: linux-riscv@lists.infradead.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, adrian.hunter@intel.com,
kan.liang@linux.intel.com, john.g.garry@oracle.com,
will@kernel.org, james.clark@linaro.org, mike.leach@linaro.org,
leo.yan@linux.dev, guoren@kernel.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, terrelln@fb.com,
mhiramat@kernel.org, changbin.du@huawei.com, amadio@gentoo.org,
yangjihong@bytedance.com, adityag@linux.ibm.com,
atrajeev@linux.vnet.ibm.com, masahiroy@kernel.org,
maobibo@loongson.cn, chenhuacai@kernel.org, kjain@linux.ibm.com,
atishp@rivosinc.com, liangshenlin@eswincomputing.com,
anup@brainfault.org, oliver.upton@linux.dev, sesse@google.com,
linux@treblig.org, cp0613@linux.alibaba.com,
dima@secretsauce.net, przemyslaw.kitszel@intel.com,
davem@davemloft.net, aleksander.lobakin@intel.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org
Subject: Re: [PATCH v4 00/20] Remove PERF_HAVE_DWARF_REGS
Date: Wed, 11 Dec 2024 22:32:30 +0000 [thread overview]
Message-ID: <173395635051.1729195.13191557882673334015.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241108234606.429459-1-irogers@google.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Namhyung Kim <namhyung@kernel.org>:
On Fri, 8 Nov 2024 15:45:45 -0800 you wrote:
> These changes were originally on top of:
> https://lore.kernel.org/lkml/20241017001354.56973-1-irogers@google.com/
>
> Prior to these patches PERF_HAVE_DWARF_REGS indicated the presence of
> dwarf-regs.c in the arch directory. dwarf-regs.c provided upto 4
> functions:
>
> [...]
Here is the summary with links:
- [v4,01/20] perf bpf-prologue: Remove unused file
https://git.kernel.org/riscv/c/2bf7692eadc5
- [v4,02/20] perf dwarf-regs: Remove PERF_HAVE_ARCH_REGS_QUERY_REGISTER_OFFSET
https://git.kernel.org/riscv/c/6ac75289b288
- [v4,03/20] perf dwarf-regs: Add EM_HOST and EF_HOST defines
https://git.kernel.org/riscv/c/ae894b77923e
- [v4,04/20] perf disasm: Add e_machine/e_flags to struct arch
https://git.kernel.org/riscv/c/cd6c9dca9d4b
- [v4,05/20] perf dwarf-regs: Pass accurate disassembly machine to get_dwarf_regnum
https://git.kernel.org/riscv/c/9fc4489a16f4
- [v4,06/20] perf dwarf-regs: Pass ELF flags to get_dwarf_regstr
https://git.kernel.org/riscv/c/a784847c2da1
- [v4,07/20] perf dwarf-regs: Move x86 dwarf-regs out of arch
https://git.kernel.org/riscv/c/bf4e799a0a33
- [v4,08/20] perf arm64: Remove dwarf-regs.c
https://git.kernel.org/riscv/c/6f8e8add5a0a
- [v4,09/20] perf arm: Remove dwarf-regs.c
https://git.kernel.org/riscv/c/0c0a20ecdf67
- [v4,10/20] perf dwarf-regs: Move csky dwarf-regs out of arch
https://git.kernel.org/riscv/c/d4a0c4f22121
- [v4,11/20] perf loongarch: Remove dwarf-regs.c
https://git.kernel.org/riscv/c/1d37bd8366d8
- [v4,12/20] perf mips: Remove dwarf-regs.c
https://git.kernel.org/riscv/c/8a768a2f6592
- [v4,13/20] perf dwarf-regs: Move powerpc dwarf-regs out of arch
https://git.kernel.org/riscv/c/285b523c2da2
- [v4,14/20] perf riscv: Remove dwarf-regs.c and add dwarf-regs-table.h
https://git.kernel.org/riscv/c/a90c4519186d
- [v4,15/20] perf s390: Remove dwarf-regs.c
https://git.kernel.org/riscv/c/b232b704a781
- [v4,16/20] perf sh: Remove dwarf-regs.c
https://git.kernel.org/riscv/c/04150f29e212
- [v4,17/20] perf sparc: Remove dwarf-regs.c
https://git.kernel.org/riscv/c/85567a2a8d42
- [v4,18/20] perf xtensa: Remove dwarf-regs.c
https://git.kernel.org/riscv/c/a4747c09507d
- [v4,19/20] perf dwarf-regs: Remove get_arch_regstr code
https://git.kernel.org/riscv/c/3ef6b89a129a
- [v4,20/20] perf build: Remove PERF_HAVE_DWARF_REGS
https://git.kernel.org/riscv/c/ddbfb6f20c1b
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:[~2024-12-11 22:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 23:45 [PATCH v4 00/20] Remove PERF_HAVE_DWARF_REGS Ian Rogers
2024-11-08 23:45 ` [PATCH v4 01/20] perf bpf-prologue: Remove unused file Ian Rogers
2024-11-08 23:45 ` [PATCH v4 02/20] perf dwarf-regs: Remove PERF_HAVE_ARCH_REGS_QUERY_REGISTER_OFFSET Ian Rogers
2024-11-08 23:45 ` [PATCH v4 03/20] perf dwarf-regs: Add EM_HOST and EF_HOST defines Ian Rogers
2024-11-08 23:45 ` [PATCH v4 04/20] perf disasm: Add e_machine/e_flags to struct arch Ian Rogers
2024-11-08 23:45 ` [PATCH v4 05/20] perf dwarf-regs: Pass accurate disassembly machine to get_dwarf_regnum Ian Rogers
2024-11-08 23:45 ` [PATCH v4 06/20] perf dwarf-regs: Pass ELF flags to get_dwarf_regstr Ian Rogers
2024-11-08 23:45 ` [PATCH v4 07/20] perf dwarf-regs: Move x86 dwarf-regs out of arch Ian Rogers
2024-11-08 23:45 ` [PATCH v4 08/20] perf arm64: Remove dwarf-regs.c Ian Rogers
2024-11-08 23:45 ` [PATCH v4 09/20] perf arm: " Ian Rogers
2024-11-08 23:45 ` [PATCH v4 10/20] perf dwarf-regs: Move csky dwarf-regs out of arch Ian Rogers
2024-11-08 23:45 ` [PATCH v4 11/20] perf loongarch: Remove dwarf-regs.c Ian Rogers
2024-11-08 23:45 ` [PATCH v4 12/20] perf mips: " Ian Rogers
2024-11-08 23:45 ` [PATCH v4 13/20] perf dwarf-regs: Move powerpc dwarf-regs out of arch Ian Rogers
2024-11-08 23:45 ` [PATCH v4 14/20] perf riscv: Remove dwarf-regs.c and add dwarf-regs-table.h Ian Rogers
2024-11-08 23:46 ` [PATCH v4 15/20] perf s390: Remove dwarf-regs.c Ian Rogers
2024-11-08 23:46 ` [PATCH v4 16/20] perf sh: " Ian Rogers
2024-11-08 23:46 ` [PATCH v4 17/20] perf sparc: " Ian Rogers
2024-11-08 23:46 ` [PATCH v4 18/20] perf xtensa: " Ian Rogers
2024-11-08 23:46 ` [PATCH v4 19/20] perf dwarf-regs: Remove get_arch_regstr code Ian Rogers
2024-11-08 23:46 ` [PATCH v4 20/20] perf build: Remove PERF_HAVE_DWARF_REGS Ian Rogers
2024-11-10 16:08 ` [PATCH v4 00/20] " Namhyung Kim
2024-12-11 22:32 ` 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=173395635051.1729195.13191557882673334015.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=acme@kernel.org \
--cc=adityag@linux.ibm.com \
--cc=adrian.hunter@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=amadio@gentoo.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=changbin.du@huawei.com \
--cc=chenhuacai@kernel.org \
--cc=cp0613@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dima@secretsauce.net \
--cc=guoren@kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linux.dev \
--cc=liangshenlin@eswincomputing.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=linux@treblig.org \
--cc=maobibo@loongson.cn \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=sesse@google.com \
--cc=terrelln@fb.com \
--cc=will@kernel.org \
--cc=yangjihong@bytedance.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).