From: Michael Forney <mforney@mforney.org>
To: 9front@9front.org
Subject: [9front] nusb(4): fix typo
Date: Sat, 23 Jan 2021 19:01:11 -0800 [thread overview]
Message-ID: <79B05B05C92B009F8B67AA0842818360@arrow.hsd1.ca.comcast.net> (raw)
diff -r 23bc19c2ceec -r b4e0e1c28d06 sys/man/4/nusb
--- a/sys/man/4/nusb Sat Jan 23 13:12:30 2021 -0800
+++ b/sys/man/4/nusb Sat Jan 23 13:15:17 2021 -0800
@@ -109,7 +109,7 @@
are formatted as 4 digit hexadecimal.
.I Csp
is the device class, subclass, protocol indentifier
-formatd as 6 digit hexadecimal.
+formatted as 6 digit hexadecimal.
.I Usbd
assigns a stable device unique name based on the
device descriptor for
reply other threads:[~2021-01-24 3:33 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=79B05B05C92B009F8B67AA0842818360@arrow.hsd1.ca.comcast.net \
--to=mforney@mforney.org \
--cc=9front@9front.org \
/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 NNTP newsgroup(s).