[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <167029621574.4417.18172654401785175878.git-patchwork-notify@kernel.org>
Date: Tue, 06 Dec 2022 03:10:15 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Guo Ren <guoren@...nel.org>
Cc: linux-riscv@...ts.infradead.org, anup@...infault.org,
paul.walmsley@...ive.com, palmer@...belt.com,
conor.dooley@...rochip.com, heiko@...ech.de, peterz@...radead.org,
arnd@...db.de, linux-arch@...r.kernel.org, keescook@...omium.org,
paulmck@...nel.org, frederic@...nel.org, nsaenzju@...hat.com,
changbin.du@...el.com, vincent.chen@...ive.com,
linux-kernel@...r.kernel.org, guoren@...ux.alibaba.com
Subject: Re: [PATCH 0/2] riscv: stacktrace: A fixup and an optimization
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@...osinc.com>:
On Wed, 9 Nov 2022 01:49:35 -0500 you wrote:
> From: Guo Ren <guoren@...ux.alibaba.com>
>
> First is a fixup for the return address pointer. The second makes
> walk_stackframe could cross the pt_regs frame.
>
> Guo Ren (2):
> riscv: stacktrace: Fixup ftrace_graph_ret_addr retp argument
> riscv: stacktrace: Make walk_stackframe cross pt_regs frame
>
> [...]
Here is the summary with links:
- [1/2] riscv: stacktrace: Fixup ftrace_graph_ret_addr retp argument
https://git.kernel.org/riscv/c/5c3022e4a616
- [2/2] riscv: stacktrace: Make walk_stackframe cross pt_regs frame
https://git.kernel.org/riscv/c/7ecdadf7f8c6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists