From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
madvenka@linux.microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 0/2] arm64: stacktrace: minor fixes
Date: Tue, 3 Aug 2021 11:05:17 +0100 [thread overview]
Message-ID: <162798357625.1498135.17761715523508973677.b4-ty@kernel.org> (raw)
In-Reply-To: <20210802164845.45506-1-mark.rutland@arm.com>
On Mon, 2 Aug 2021 17:48:43 +0100, Mark Rutland wrote:
> These patches address a couple of minor issues I spotted while reviewing
> arm64's stacktrace code. Patch 1 is a simple comment fix, and patch 2
> addresses an imbalance across the main stack and the fgraph return
> stack.
>
> Thanks,
> Mark
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/2] arm64: stacktrace: fix comment
https://git.kernel.org/arm64/c/8d5903f45714
[2/2] arm64: stacktrace: avoid tracing arch_stack_walk()
https://git.kernel.org/arm64/c/0c32706dac1b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-08-03 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 16:48 [PATCH 0/2] arm64: stacktrace: minor fixes Mark Rutland
2021-08-02 16:48 ` [PATCH 1/2] arm64: stacktrace: fix comment Mark Rutland
2021-08-02 16:53 ` Mark Brown
2021-08-02 16:48 ` [PATCH 2/2] arm64: stacktrace: avoid tracing arch_stack_walk() Mark Rutland
2021-08-02 17:18 ` Mark Brown
2021-08-03 10:05 ` Will Deacon [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=162798357625.1498135.17761715523508973677.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=madvenka@linux.microsoft.com \
--cc=mark.rutland@arm.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).