From: Kevin Hao <haokexin@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v2 0/2] arm64: Fix the call trace when running kgdb test suite
Date: Thu, 2 Jul 2020 17:40:51 +0800 [thread overview]
Message-ID: <20200702094051.GD1910209@pek-khao-d2.corp.ad.wrs.com> (raw)
In-Reply-To: <20200417103212.45812-1-haokexin@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 752 bytes --]
On Fri, Apr 17, 2020 at 06:32:10PM +0800, Kevin Hao wrote:
> Hi guys,
>
> This fixes a call trace when running the kgdb test suite:
> # echo kgdbts=V1 > /sys/module/kgdbts/parameters/kgdbts
Ping.
Thanks,
Kevin
>
> v2:
> - Add a patch to fix a typo in el1_dbg()
> - Use the method as suggested by Mark.
>
> v1:
> https://lore.kernel.org/r/20200401052107.36076-1-haokexin@gmail.com
>
>
> Kevin Hao (2):
> arm64: entry: Fix the typo in the comment of el1_dbg()
> arm64: debug: Always update the IRQ tracing in debug_exception_enter()
>
> arch/arm64/kernel/entry-common.c | 2 +-
> arch/arm64/mm/fault.c | 8 ++------
> 2 files changed, 3 insertions(+), 7 deletions(-)
>
> --
> 2.26.0
>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-02 9:42 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 ` Kevin Hao [this message]
2020-07-08 22:02 ` [PATCH v2 0/2] arm64: Fix the call trace when running kgdb test suite Will Deacon
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=20200702094051.GD1910209@pek-khao-d2.corp.ad.wrs.com \
--to=haokexin@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=will@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