From: patchwork-bot+linux-riscv@kernel.org
To: Guo Ren <guoren@kernel.org>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
conor.dooley@microchip.com, heiko@sntech.de,
peterz@infradead.org, arnd@arndb.de, linux-arch@vger.kernel.org,
keescook@chromium.org, paulmck@kernel.org, frederic@kernel.org,
nsaenzju@redhat.com, changbin.du@intel.com,
vincent.chen@sifive.com, linux-kernel@vger.kernel.org,
guoren@linux.alibaba.com
Subject: Re: [PATCH 0/2] riscv: stacktrace: A fixup and an optimization
Date: Tue, 06 Dec 2022 03:10:15 +0000 [thread overview]
Message-ID: <167029621574.4417.18172654401785175878.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221109064937.3643993-1-guoren@kernel.org>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 9 Nov 2022 01:49:35 -0500 you wrote:
> From: Guo Ren <guoren@linux.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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-12-06 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 6:49 [PATCH 0/2] riscv: stacktrace: A fixup and an optimization guoren
2022-11-09 6:49 ` [PATCH 1/2] riscv: stacktrace: Fixup ftrace_graph_ret_addr retp argument guoren
2022-11-09 6:49 ` [PATCH 2/2] riscv: stacktrace: Make walk_stackframe cross pt_regs frame guoren
2022-11-21 9:53 ` Guo Ren
2022-11-21 11:49 ` Guo Ren
2022-12-06 2:59 ` Palmer Dabbelt
2022-12-06 3:30 ` Guo Ren
2022-12-06 2:59 ` [PATCH 0/2] riscv: stacktrace: A fixup and an optimization Palmer Dabbelt
2022-12-06 3:10 ` 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=167029621574.4417.18172654401785175878.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=anup@brainfault.org \
--cc=arnd@arndb.de \
--cc=changbin.du@intel.com \
--cc=conor.dooley@microchip.com \
--cc=frederic@kernel.org \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=heiko@sntech.de \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nsaenzju@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=vincent.chen@sifive.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