From: Will Deacon <will@kernel.org>
To: Ada Couprie Diaz <ada.coupriediaz@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
"Luis Claudio R . Goncalves" <lgoncalv@redhat.com>
Subject: Re: [PATCH v4 01/13] arm64: debug: clean up single_step_handler logic
Date: Fri, 27 Jun 2025 16:44:50 +0100 [thread overview]
Message-ID: <aF68crbeST5WJMap@willie-the-truck> (raw)
In-Reply-To: <20250620211207.773980-2-ada.coupriediaz@arm.com>
On Fri, Jun 20, 2025 at 10:11:55PM +0100, Ada Couprie Diaz wrote:
> Remove the unnecessary boolean which always checks if the handler was found
> and return early instead.
>
> Signed-off-by: Ada Couprie Diaz <ada.coupriediaz@arm.com>
> Tested-by: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
> Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> ---
> arch/arm64/kernel/debug-monitors.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
Reviewed-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2025-06-27 16:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 21:11 [PATCH v4 00/13] arm64: debug: remove hook registration, split exception entry Ada Couprie Diaz
2025-06-20 21:11 ` [PATCH v4 01/13] arm64: debug: clean up single_step_handler logic Ada Couprie Diaz
2025-06-27 15:44 ` Will Deacon [this message]
2025-06-20 21:11 ` [PATCH v4 02/13] arm64: refactor aarch32_break_handler() Ada Couprie Diaz
2025-06-27 15:45 ` Will Deacon
2025-06-20 21:11 ` [PATCH v4 03/13] arm64: debug: call software breakpoint handlers statically Ada Couprie Diaz
2025-06-27 15:45 ` Will Deacon
2025-06-20 21:11 ` [PATCH v4 04/13] arm64: debug: call step " Ada Couprie Diaz
2025-06-27 15:45 ` Will Deacon
2025-06-20 21:11 ` [PATCH v4 05/13] arm64: debug: remove break/step handler registration infrastructure Ada Couprie Diaz
2025-06-27 15:45 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 06/13] arm64: entry: Add entry and exit functions for debug exceptions Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 07/13] arm64: debug: split hardware breakpoint exception entry Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 08/13] arm64: debug: refactor reinstall_suspended_bps() Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 09/13] arm64: debug: split single stepping exception entry Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 10/13] arm64: debug: split hardware watchpoint " Ada Couprie Diaz
2025-06-27 15:46 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 11/13] arm64: debug: split brk64 " Ada Couprie Diaz
2025-06-27 15:47 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 12/13] arm64: debug: split bkpt32 " Ada Couprie Diaz
2025-06-27 15:47 ` Will Deacon
2025-06-20 21:12 ` [PATCH v4 13/13] arm64: debug: remove debug exception registration infrastructure Ada Couprie Diaz
2025-06-27 15:47 ` Will Deacon
2025-06-27 15:48 ` [PATCH v4 00/13] arm64: debug: remove hook registration, split exception entry Will Deacon
2025-06-27 17:27 ` Ada Couprie Diaz
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=aF68crbeST5WJMap@willie-the-truck \
--to=will@kernel.org \
--cc=ada.coupriediaz@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=lgoncalv@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.