From: Hemanth Selam <hemanth.selam@gmail.com>
To: David Heidelberg <david@ixit.cz>
Cc: linux-kernel@vger.kernel.org, oe-linux-nfc@lists.linux.dev
Subject: Re: [PATCH] nfc: fix typo "occured" in comments
Date: Mon, 7 Sep 2026 10:09:32 +0530 [thread overview]
Message-ID: <20260907043933.33452-3-hemanth.selam@gmail.com> (raw)
In-Reply-To: <dc3ba062-a548-4a9b-984e-a8f2473606dd@ixit.cz>
You are right, and codespell is in fact where these came from - I ran it
across the tree and fed the results through checkpatch. The model was used
for the packaging around that, not for finding the words, which in
hindsight was not a good use of it.
Thanks for the extra hits. If you would like them fixed I can fold
drivers/nfc/fdp/fdp.c nd ==> and
drivers/nfc/fdp/i2c.c:270 inclue ==> include
into a v2 of this patch, though "nd" there is part of "2nd" in at least
some of those lines and needs reading before it is changed - which is the
mistake I have already made elsewhere in this series. Let me know if you
want the v2.
prev parent reply other threads:[~2026-09-07 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 11:46 Hemanth Selam
2026-09-04 12:00 ` David Heidelberg
2026-09-07 4:39 ` Hemanth Selam [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=20260907043933.33452-3-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=david@ixit.cz \
--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®