From: Miles Krause <mileskrause5200@gmail.com>
To: Mark Greer <mgreer@animalcreek.com>,
David Heidelberg <david+nfc@ixit.cz>
Cc: linux-wireless@vger.kernel.org, oe-linux-nfc@lists.linux.dev,
linux-kernel@vger.kernel.org,
Miles Krause <mileskrause5200@gmail.com>
Subject: [PATCH] nfc: trf7970a: fix comment typos
Date: Thu, 30 Apr 2026 20:35:45 -0400 [thread overview]
Message-ID: <20260501003548.6838-1-mileskrause5200@gmail.com> (raw)
Fix a few spelling mistakes in comments.
Signed-off-by: Miles Krause <mileskrause5200@gmail.com>
---
drivers/nfc/trf7970a.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/nfc/trf7970a.c b/drivers/nfc/trf7970a.c
index 08c27bb438b5..f22e091019de 100644
--- a/drivers/nfc/trf7970a.c
+++ b/drivers/nfc/trf7970a.c
@@ -61,15 +61,15 @@
* support that. So, if an abort is received before trf7970a_send_cmd()
* has sent the command to the tag, it simply returns -ECANCELED. If the
* command has already been sent to the tag, then the driver continues
- * normally and recieves the response data (or error) but just before
+ * normally and receives the response data (or error) but just before
* sending the data upstream, it frees the rx_skb and sends -ECANCELED
* upstream instead. If the command failed, that error will be sent
* upstream.
*
- * When recieving data from a tag and the interrupt status register has
+ * When receiving data from a tag and the interrupt status register has
* only the SRX bit set, it means that all of the data has been received
* (once what's in the fifo has been read). However, depending on timing
- * an interrupt status with only the SRX bit set may not be recived. In
+ * an interrupt status with only the SRX bit set may not be received. In
* those cases, the timeout mechanism is used to wait 20 ms in case more
* data arrives. After 20 ms, it is assumed that all of the data has been
* received and the accumulated rx data is sent upstream. The
base-commit: 08d0d3466664000ba0670e0ef0d447f23459e0d4
--
2.54.0
reply other threads:[~2026-05-01 0:35 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=20260501003548.6838-1-mileskrause5200@gmail.com \
--to=mileskrause5200@gmail.com \
--cc=david+nfc@ixit.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--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