From: Oliver Neukum <oneukum@suse.de>
To: Chris Rorvick <chris@rorvick.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: Fix typo in `struct usb_host_interface' comment
Date: Fri, 16 Jan 2015 09:10:00 +0100 [thread overview]
Message-ID: <1421395800.15673.0.camel@linux-0dmf.site> (raw)
In-Reply-To: <CAEUsAPZeK18xBKawK5GVmhxrOwi3ZNOP-x9fUrkdEgWj10tUbw@mail.gmail.com>
On Thu, 2015-01-15 at 17:47 -0600, Chris Rorvick wrote:
> I think understand your comment now so I will respond more
> specifically:
> This is a typo precisely because `bNumEndpoint' is not consistent with
> the specification, nor is it consistent with the definition of `struct
> usb_interface_descriptor'. The specification and the structure both
> use
> `bNumEndpoints'.
Sorry, I stand corrected. The patch is good.
Regards
Oliver
prev parent reply other threads:[~2015-01-16 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 3:52 [PATCH] usb: Fix typo in `struct usb_host_interface' comment Chris Rorvick
2015-01-15 11:03 ` Oliver Neukum
2015-01-15 12:54 ` Chris Rorvick
2015-01-15 23:47 ` Chris Rorvick
2015-01-16 8:10 ` Oliver Neukum [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=1421395800.15673.0.camel@linux-0dmf.site \
--to=oneukum@suse.de \
--cc=chris@rorvick.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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