mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Haowen Bai <baihaowen@meizu.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Phillip Potter <phil@philpotter.co.uk>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: r8188eu: Fix misspelling in comment
Date: Wed, 30 Mar 2022 08:39:08 +0200	[thread overview]
Message-ID: <YkP7DGP+nbo2VJ+Z@kroah.com> (raw)
In-Reply-To: <1648621413-1263-1-git-send-email-baihaowen@meizu.com>

On Wed, Mar 30, 2022 at 02:23:33PM +0800, Haowen Bai wrote:
> This patch fixes some spelling typo in error message reported by checkpatch.pl
> 
> WARNING: 'cacluated' may be misspelled - perhaps 'calculated'?
> WARNING: 'cacluated' may be misspelled - perhaps 'calculated'?
> WARNING: 'writting' may be misspelled - perhaps 'writing'?
> WARNING: 'defualt' may be misspelled - perhaps 'default'?
> WARNING: 'Caculate' may be misspelled - perhaps 'Calculate'?
> WARNING: 'accordign' may be misspelled - perhaps 'according'?
> WARNING: 'regster' may be misspelled - perhaps 'register'?
> WARNING: 'Wirte' may be misspelled - perhaps 'Write'?
> WARNING: 'Tranceiver' may be misspelled - perhaps 'Transceiver'?
> WARNING: 'Tranceiver' may be misspelled - perhaps 'Transceiver'?
> WARNING: 'Tranceiver' may be misspelled - perhaps 'Transceiver'?
> WARNING: 'Tranceiver' may be misspelled - perhaps 'Transceiver'?

Please break this up into one-patch-per-misspelled-word.

thanks,

greg k-h

  reply	other threads:[~2022-03-30  6:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30  6:23 Haowen Bai
2022-03-30  6:39 ` Greg Kroah-Hartman [this message]
2022-03-30  7:27   ` [PATCH V2] staging: r8188eu: Fix misspelling in comment "Tranceiver" -> "Transceiver" Haowen Bai
  -- strict thread matches above, loose matches on Subject: below --
2022-03-21  2:55 [PATCH] staging: r8188eu: Fix misspelling in comment Haowen Bai
2022-03-29 14:52 ` Greg KH
2022-03-30  1:42   ` baihaowen

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=YkP7DGP+nbo2VJ+Z@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=baihaowen@meizu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=phil@philpotter.co.uk \
    /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®