From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: akpm@linux-foundation.org, trivial@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/Kconfig: Update HAVE_RELIABLE_STACKTRACE description
Date: Mon, 20 Jan 2020 11:32:28 -0600 [thread overview]
Message-ID: <20200120173228.5nxa72ri5msywiop@treble> (raw)
In-Reply-To: <20200120154042.9934-1-mbenes@suse.cz>
On Mon, Jan 20, 2020 at 04:40:42PM +0100, Miroslav Benes wrote:
> save_stack_trace_tsk_reliable() is not the only function providing the
> reliable stack traces anymore. Architecture might define ARCH_STACKWALK
> which provides a newer stack walking interface and has
> arch_stack_walk_reliable() function. Update the description accordingly.
>
> Signed-off-by: Miroslav Benes <mbenes@suse.cz>
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
--
Josh
prev parent reply other threads:[~2020-01-20 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 15:40 [PATCH] arch/Kconfig: Update HAVE_RELIABLE_STACKTRACE description Miroslav Benes
2020-01-20 17:32 ` Josh Poimboeuf [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=20200120173228.5nxa72ri5msywiop@treble \
--to=jpoimboe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=trivial@kernel.org \
/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).