From: David Heidelberg <david@ixit.cz>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: linux-kernel@vger.kernel.org, oe-linux-nfc@lists.linux.dev
Subject: Re: [PATCH] nfc: fix typo "occured" in comments
Date: Fri, 4 Sep 2026 14:00:31 +0200 [thread overview]
Message-ID: <dc3ba062-a548-4a9b-984e-a8f2473606dd@ixit.cz> (raw)
In-Reply-To: <20260904114632.31336-1-hemanth.selam@gmail.com>
On 04/09/2026 13:46, Hemanth Selam wrote:
> Correct "occured" to "occurred", reported by scripts/checkpatch.pl using
> the misspelling list in scripts/spelling.txt. Only touches comments, no
> code changes.
>
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
> drivers/nfc/microread/i2c.c | 2 +-
> drivers/nfc/pn544/i2c.c | 2 +-
> drivers/nfc/st21nfca/i2c.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
Heya, you don't need Artificial Intelligence for that, you can use
$ codespell drivers/nfc/*
drivers/nfc/fdp/fdp.c:123: nd ==> and, 2nd
drivers/nfc/fdp/fdp.c:126: nd ==> and, 2nd
drivers/nfc/fdp/fdp.c:127: nd ==> and, 2nd
drivers/nfc/fdp/fdp.c:138: nd ==> and, 2nd
drivers/nfc/fdp/i2c.c:270: inclue ==> include
drivers/nfc/microread/i2c.c:42: occured ==> occurred
drivers/nfc/nfcmrvl/uart.c:180: sate ==> state
drivers/nfc/pn533/uart.c:35: propability ==> probability
drivers/nfc/pn533/uart.c:144: errornous ==> erroneous
drivers/nfc/pn533/usb.c:215: stange ==> strange, stage, stance
drivers/nfc/pn544/i2c.c:172: occured ==> occurred
drivers/nfc/port100.c:104: Theses ==> These, Thesis
drivers/nfc/st-nci/i2c.c:3: familly ==> family
drivers/nfc/st-nci/ndlc.c:111: aknowledge ==> acknowledge
drivers/nfc/st-nci/ndlc.c:172: aknowledge ==> acknowledge
drivers/nfc/st-nci/spi.c:215: functionnalities ==> functionalities
drivers/nfc/st21nfca/core.c:468: respone ==> response, respond
drivers/nfc/st21nfca/i2c.c:28: mecanism ==> mechanism
drivers/nfc/st21nfca/i2c.c:69: occured ==> occurred
drivers/nfc/st21nfca/i2c.c:365: mecanism ==> mechanism
drivers/nfc/st21nfca/i2c.c:385: corrupeted ==> corrupted
drivers/nfc/st95hf/core.c:455: milisecond ==> millisecond
drivers/nfc/st95hf/core.c:487: milisecond ==> millisecond
drivers/nfc/st95hf/core.c:493: milisecond ==> millisecond
drivers/nfc/st95hf/core.c:524: milisecond ==> millisecond
drivers/nfc/st95hf/core.c:634: cofigure ==> configure
drivers/nfc/st95hf/core.c:787: cant ==> can't
Feel free to check validity and fix everything relevant (sometimes it report
false-positive).
David
prev parent reply other threads:[~2026-09-04 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 11:46 Hemanth Selam
2026-09-04 12:00 ` David Heidelberg [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=dc3ba062-a548-4a9b-984e-a8f2473606dd@ixit.cz \
--to=david@ixit.cz \
--cc=hemanth.selam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
/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®