From: dustinb@codeaurora•org (Dustin Brown)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] Export save_stack_trace_tsk for ARM and ARM64
Date: Mon, 12 Jun 2017 15:24:31 -0700 [thread overview]
Message-ID: <20170612222431.1854-1-dustinb@codeaurora.org> (raw)
To help in debugging driver modules on ARM platforms, export
save_stack_trace_tsk() for ARM and ARM64 architectures.
---
arch/arm/kernel/stacktrace.c | 1 +
arch/arm64/kernel/stacktrace.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm/kernel/stacktrace.c b/arch/arm/kernel/stacktrace.c
index 3a2fa203637a..564bb468b7ba 100644
--- a/arch/arm/kernel/stacktrace.c
+++ b/arch/arm/kernel/stacktrace.c
@@ -171,6 +171,7 @@ void save_stack_trace_tsk(struct task_struct *tsk, struct stack_trace *trace)
{
__save_stack_trace(tsk, trace, 1);
}
+EXPORT_SYMBOL_GPL(save_stack_trace_tsk);
void save_stack_trace(struct stack_trace *trace)
{
diff --git a/arch/arm64/kernel/stacktrace.c b/arch/arm64/kernel/stacktrace.c
index feac80c22f61..09d37d66b630 100644
--- a/arch/arm64/kernel/stacktrace.c
+++ b/arch/arm64/kernel/stacktrace.c
@@ -210,6 +210,7 @@ void save_stack_trace_tsk(struct task_struct *tsk, struct stack_trace *trace)
put_task_stack(tsk);
}
+EXPORT_SYMBOL_GPL(save_stack_trace_tsk);
void save_stack_trace(struct stack_trace *trace)
{
--
2.12.2
next reply other threads:[~2017-06-12 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 22:24 Dustin Brown [this message]
2017-06-13 8:50 ` [PATCH] Export save_stack_trace_tsk for ARM and ARM64 Will Deacon
2017-06-13 17:33 ` [PATCH 1/2] arm: Export save_stack_trace_tsk() Dustin Brown
2017-06-13 17:33 ` [PATCH 2/2] arm64: " Dustin Brown
2017-06-13 17:44 ` Will Deacon
2017-06-13 18:16 ` Russell King - ARM Linux
2017-06-13 18:40 ` [PATCH 1/2] arm: " Dustin Brown
2017-06-13 18:40 ` [PATCH 2/2] arm64: " Dustin Brown
2017-07-12 18:06 ` [PATCH 1/2] arm: " Dustin Brown
2017-06-14 10:06 ` [PATCH 2/2] arm64: " Will Deacon
2017-06-14 16:51 ` Dustin Brown
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=20170612222431.1854-1-dustinb@codeaurora.org \
--to=dustinb@codeaurora$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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