From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>, Jisheng Zhang <jszhang3@mail.ustc.edu.cn>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: remove HAVE_DEBUG_BUGVERBOSE
Date: Fri, 23 Apr 2021 18:10:08 +0100 [thread overview]
Message-ID: <161919777114.6013.3497530317233037222.b4-ty@arm.com> (raw)
In-Reply-To: <20210418215231.563d4b72@xhacker>
On Sun, 18 Apr 2021 21:52:31 +0800, Jisheng Zhang wrote:
> After commit 9fb7410f955f ("arm64/BUG: Use BRK instruction for generic
> BUG traps"), arm64 has switched to generic BUG implementation, so
> there's no need to select HAVE_DEBUG_BUGVERBOSE.
Applied to arm64 (for-next/core), thanks!
[1/1] arm64: remove HAVE_DEBUG_BUGVERBOSE
https://git.kernel.org/arm64/c/4139cf940d52
--
Catalin
prev parent reply other threads:[~2021-04-23 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 13:52 [PATCH] arm64: remove HAVE_DEBUG_BUGVERBOSE Jisheng Zhang
2021-04-22 13:01 ` Will Deacon
2021-04-23 17:10 ` Catalin Marinas [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=161919777114.6013.3497530317233037222.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=jszhang3@mail.ustc.edu.cn \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).