From: Will Deacon <will@kernel.org>
To: Kevin Hao <haokexin@gmail.com>, linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2 0/2] arm64: Fix the call trace when running kgdb test suite
Date: Wed, 8 Jul 2020 23:02:34 +0100 [thread overview]
Message-ID: <159424108956.2036212.1249632670220812634.b4-ty@kernel.org> (raw)
In-Reply-To: <20200417103212.45812-1-haokexin@gmail.com>
On Fri, 17 Apr 2020 18:32:10 +0800, Kevin Hao wrote:
> This fixes a call trace when running the kgdb test suite:
> # echo kgdbts=V1 > /sys/module/kgdbts/parameters/kgdbts
>
> v2:
> - Add a patch to fix a typo in el1_dbg()
> - Use the method as suggested by Mark.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: entry: Fix the typo in the comment of el1_dbg()
https://git.kernel.org/arm64/c/b8c1c9fe6a04
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
next prev parent reply other threads:[~2020-07-08 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 10:32 [PATCH v2 0/2] arm64: Fix the call trace when running kgdb test suite Kevin Hao
2020-04-17 10:32 ` [PATCH 1/2] arm64: entry: Fix the typo in the comment of el1_dbg() Kevin Hao
2020-04-17 14:10 ` Mark Rutland
2020-04-17 10:32 ` [PATCH 2/2] arm64: debug: Always update the IRQ tracing in debug_exception_enter() Kevin Hao
2020-07-02 9:40 ` [PATCH v2 0/2] arm64: Fix the call trace when running kgdb test suite Kevin Hao
2020-07-08 22:02 ` Will Deacon [this message]
2020-07-09 12:55 ` Kevin Hao
2020-07-09 13:03 ` Will Deacon
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=159424108956.2036212.1249632670220812634.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=haokexin@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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