From: Zhang Jiaming <jiaming@nfschina.com>
To: oss@buserror.net, mpe@ellerman.id.au, benh@kernel.crashing.org,
paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
liqiong@nfschina.com, renyu@nfschina.com,
Zhang Jiaming <jiaming@nfschina.com>
Subject: [PATCH] powerpc/sgy_cts1000: Fix typo in comments
Date: Fri, 1 Jul 2022 17:24:45 +0800 [thread overview]
Message-ID: <20220701092445.16871-1-jiaming@nfschina.com> (raw)
There is a typo ('wont') in comments.
Fix it.
Signed-off-by: Zhang Jiaming <jiaming@nfschina.com>
---
arch/powerpc/platforms/85xx/sgy_cts1000.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/platforms/85xx/sgy_cts1000.c b/arch/powerpc/platforms/85xx/sgy_cts1000.c
index 98ae64075193..a920852703ba 100644
--- a/arch/powerpc/platforms/85xx/sgy_cts1000.c
+++ b/arch/powerpc/platforms/85xx/sgy_cts1000.c
@@ -29,7 +29,7 @@ static const struct of_device_id child_match[] = {
static void gpio_halt_wfn(struct work_struct *work)
{
- /* Likely wont return */
+ /* Likely won't return */
orderly_poweroff(true);
}
static DECLARE_WORK(gpio_halt_wq, gpio_halt_wfn);
@@ -51,7 +51,7 @@ static void __noreturn gpio_halt_cb(void)
printk(KERN_INFO "gpio-halt: triggering GPIO.\n");
- /* Probably wont return */
+ /* Probably won't return */
gpio_set_value(gpio, trigger);
panic("Halt failed\n");
@@ -147,7 +147,7 @@ static int gpio_halt_remove(struct platform_device *pdev)
static const struct of_device_id gpio_halt_match[] = {
/* We match on the gpio bus itself and scan the children since they
- * wont be matched against us. We know the bus wont match until it
+ * won't be matched against us. We know the bus won't match until it
* has been registered too. */
{
.compatible = "fsl,qoriq-gpio",
--
2.25.1
reply other threads:[~2022-07-01 9:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220701092445.16871-1-jiaming@nfschina.com \
--to=jiaming@nfschina.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liqiong@nfschina.com \
--cc=mpe@ellerman.id.au \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--cc=renyu@nfschina.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®