From: <Conor.Dooley@microchip.com>
To: <yuanjilin@cdjrlc.com>, <will@kernel.org>, <mark.rutland@arm.com>
Cc: <linux@armlinux.org.uk>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm:kernel:Fix typo in comment
Date: Wed, 22 Jun 2022 10:04:20 +0000 [thread overview]
Message-ID: <a686e9da-c825-5f53-1320-65be4cb0b8af@microchip.com> (raw)
In-Reply-To: <20220622083701.20973-1-yuanjilin@cdjrlc.com>
On 22/06/2022 09:37, Jilin Yuan wrote:
> Delete the redundant word 'ARM'.
>
> Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
> ---
> arch/arm/kernel/hw_breakpoint.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/kernel/hw_breakpoint.c b/arch/arm/kernel/hw_breakpoint.c
> index 054e9199f30d..0b3c8f2ff7b0 100644
> --- a/arch/arm/kernel/hw_breakpoint.c
> +++ b/arch/arm/kernel/hw_breakpoint.c
> @@ -199,7 +199,7 @@ static int get_num_wrps(void)
> * know which watchpoint fired. In the future we can either add a
> * disassembler and address generation emulator, or we can insert a
> * check to see if the DFAR is set on watchpoint exception entry
> - * [the ARM ARM states that the DFAR is UNKNOWN, but experience shows
> + * [the ARM states that the DFAR is UNKNOWN, but experience shows
This isnt a duplicate is it? It's The ARM Arch. Reference Manual, no?
Same would apply to your other duplicate removals for ARM I guess.
> * that it is set on some implementations].
> */
> if (get_debug_arch() < ARM_DEBUG_ARCH_V7_1)
prev parent reply other threads:[~2022-06-22 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 8:37 Jilin Yuan
2022-06-22 10:04 ` Conor.Dooley [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=a686e9da-c825-5f53-1320-65be4cb0b8af@microchip.com \
--to=conor.dooley@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
--cc=yuanjilin@cdjrlc.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
all inboxes | Powered by JetHome®