From: Grant Erickson <gerickson@nuovations.com>
To: connman@lists.linux.dev
Subject: [PATCH] connection: Fix typo in @file comment.
Date: Thu, 7 Dec 2023 17:27:16 -0800 [thread overview]
Message-ID: <20231208012716.1097174-1-gerickson@nuovations.com> (raw)
This fixes a minor grammatical typo in the @file comment.
---
src/connection.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/connection.c b/src/connection.c
index 0c1bdba7f515..30e7d736e1e0 100644
--- a/src/connection.c
+++ b/src/connection.c
@@ -32,7 +32,7 @@
* gateway routes and then uses notifications from the kernel
* Routing Netlink (rtnl) to confirm and "activate" those
* routes. Likewise, Connection Manager removes/clears/deletes
- * gateway routes an then uses notifications from the kernel
+ * gateway routes and then uses notifications from the kernel
* Routing Netlink (rtnl) to confirm and "inactivate" those
* routes. The following is the state machine for that lifecycle:
*
--
2.42.0
next reply other threads:[~2023-12-08 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 1:27 Grant Erickson [this message]
2023-12-08 19:04 ` [PATCH] connection: Fix typo in @file comment Marcel Holtmann
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=20231208012716.1097174-1-gerickson@nuovations.com \
--to=gerickson@nuovations.com \
--cc=connman@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).