From: "Slark Xiao" <slark_xiao@163.com>
To: "Conor Dooley" <mail@conchuod.ie>
Cc: monstr@monstr.eu, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] microblaze: Fix typo in comment
Date: Thu, 21 Jul 2022 14:43:42 +0800 (CST) [thread overview]
Message-ID: <7591e9f.1f6c.1821f7f7405.Coremail.slark_xiao@163.com> (raw)
In-Reply-To: <f55b4d0b-c9b8-e4b8-9a1d-468f6a22128d@conchuod.ie>
Hi Conor,
Thanks for your reply.
Actually I didn't get your point of 'Surely this should be "s/the the/like the/, no?'.
Do you mean this is NOT a TYPO, but like a change which we use 'the/' instead of 'the the/'?
Thanks!
At 2022-07-21 14:33:32, "Conor Dooley" <mail@conchuod.ie> wrote:
>
>On 21/07/2022 03:51, Slark Xiao wrote:
>> Fix typo in the comment
>>
>> Signed-off-by: Slark Xiao <slark_xiao@163.com>
>> ---
>> arch/microblaze/kernel/entry.S | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/microblaze/kernel/entry.S b/arch/microblaze/kernel/entry.S
>> index b179f8f6d287..8651fe351276 100644
>> --- a/arch/microblaze/kernel/entry.S
>> +++ b/arch/microblaze/kernel/entry.S
>> @@ -456,7 +456,7 @@ TRAP_return: /* Make global symbol for debugging */
>>
>>
>> /* This the initial entry point for a new child thread, with an appropriate
>> - stack in place that makes it look the the child is in the middle of an
>> + stack in place that makes it look the child is in the middle of an
>
>This is /a/ fix, but I don't think it is the right one for this comment.
>Surely this should be "s/the the/like the/, no?
>Thanks,
>Conor.
>
>> syscall. This function is actually `returned to' from switch_thread
>> (copy_thread makes ret_from_fork the return address in each new thread's
>> saved context). */
next prev parent reply other threads:[~2022-07-21 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 2:51 Slark Xiao
2022-07-21 6:33 ` Conor Dooley
2022-07-21 6:43 ` Slark Xiao [this message]
2022-07-21 6:53 ` Conor Dooley
2022-07-21 7:08 ` Slark Xiao
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=7591e9f.1f6c.1821f7f7405.Coremail.slark_xiao@163.com \
--to=slark_xiao@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@conchuod.ie \
--cc=monstr@monstr.eu \
/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®