From: Tech Zhou <zhouinamerica@gmail.com>
To: Karan Tilak Kumar <kartilak@cisco.com>,
Sesidhar Baddela <sebaddel@cisco.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Fix spelling error in arch/powerpc/kernel/traps.c
Date: Fri, 20 Aug 2021 14:59:11 -0400 [thread overview]
Message-ID: <CAJwUSPsYzRpGkCXXHgqPW25w-rSAoNwRPYmUmbGx=VffThWFyA@mail.gmail.com> (raw)
I found a spelling error in arch/powerpc/kernel/traps.c. Please let me
know if you have any concerns / questions. This is my first patch!
Signed-off-by: Changjun Zhou <zhouinamerica@gmail.com>
---
arch/powerpc/kernel/traps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/traps.c b/arch/powerpc/kernel/traps.c
index d56254f05e17..7355db219269 100644
--- a/arch/powerpc/kernel/traps.c
+++ b/arch/powerpc/kernel/traps.c
@@ -1522,7 +1522,7 @@ static void do_program_check(struct pt_regs *regs)
* SIGILL. The subsequent cases all relate to emulating instructions
* which we should only do for userspace. We also do not want to enable
* interrupts for kernel faults because that might lead to further
- * faults, and loose the context of the original exception.
+ * faults, and lose the context of the original exception.
*/
if (!user_mode(regs))
goto sigill;
--
next reply other threads:[~2021-08-20 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 18:59 Tech Zhou [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-20 18:05 [PATCH] Fix spelling error in arch/powerpc/kernel/traps.c Tech Zhou
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='CAJwUSPsYzRpGkCXXHgqPW25w-rSAoNwRPYmUmbGx=VffThWFyA@mail.gmail.com' \
--to=zhouinamerica@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=kartilak@cisco.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sebaddel@cisco.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;
as well as URLs for NNTP newsgroup(s).