From: Randy Dunlap <rdunlap@infradead.org>
To: Karl Mehltretter <kmehltretter@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
linux-usb@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: usbmon: Fix a typo in the example
Date: Sat, 5 Sep 2026 14:16:50 -0700 [thread overview]
Message-ID: <4b3da317-38b7-4a98-a46a-7bc308de1546@infradead.org> (raw)
In-Reply-To: <20260905075609.32879-1-kmehltretter@gmail.com>
On 9/5/26 12:56 AM, Karl Mehltretter wrote:
> struct ubsmon_packet does not exist; the name is struct usbmon_packet.
>
> Use struct usbmon_packet.
>
> Fixes: 6f23ee1fefdc ("USB: add binary API to usbmon")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
thanks.
> ---
> Documentation/usb/usbmon.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/usb/usbmon.rst b/Documentation/usb/usbmon.rst
> index 6d5ec1e62d09..667b84d3ae56 100644
> --- a/Documentation/usb/usbmon.rst
> +++ b/Documentation/usb/usbmon.rst
> @@ -361,7 +361,7 @@ Then, execute a loop similar to the one written in pseudo-code below::
> ioctl(fd, MON_IOCX_MFETCH, &fetch); // Process errors, too
> nflush = fetch.nfetch; // This many packets to flush when done
> for (i = 0; i < nflush; i++) {
> - hdr = (struct ubsmon_packet *) &mmap_area[vec[i]];
> + hdr = (struct usbmon_packet *) &mmap_area[vec[i]];
> if (hdr->type == '@') // Filler packet
> continue;
> caddr_t data = &mmap_area[vec[i]] + 64;
--
~Randy
prev parent reply other threads:[~2026-09-05 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 7:56 [PATCH] docs: usbmon: Fix a typo in the example Karl Mehltretter
2026-09-05 21:16 ` Randy Dunlap [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=4b3da317-38b7-4a98-a46a-7bc308de1546@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kmehltretter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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