From: Sergei Shtylyov <sshtylyov@mvista.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: mfm@muteddisk.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]staging: usbip: Fix typos.
Date: Mon, 30 Jul 2012 20:34:59 +0400 [thread overview]
Message-ID: <5016B7B3.2040702@mvista.com> (raw)
In-Reply-To: <1343658202-19083-1-git-send-email-justinmattock@gmail.com>
Hello.
On 07/30/2012 06:23 PM, Justin P. Mattock wrote:
> From: "Justin P. Mattock" <justinmattock@gmail.com>
> Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
> ---
> The below patch fixes typos found while reading through staging: usbip
Unfortunately, it introduces some new instead. :-)
> diff --git a/drivers/staging/usbip/vhci_hcd.c b/drivers/staging/usbip/vhci_hcd.c
> index 12a9a5f..dd15dc0 100644
> --- a/drivers/staging/usbip/vhci_hcd.c
> +++ b/drivers/staging/usbip/vhci_hcd.c
> @@ -828,11 +828,11 @@ static void vhci_shutdown_connection(struct usbip_device *ud)
> * disable endpoints. pending urbs are unlinked(dequeued).
> *
> * NOTE: After calling rh_port_disconnect(), the USB device drivers of a
> - * deteched device should release used urbs in a cleanup function(i.e.
> + * detached device should release used urbs in a cleanup function(i.e.
Space is needed before "(i.e.".
> * xxx_disconnect()). Therefore, vhci_hcd does not need to release
> * pushed urbs and their private data in this function.
> *
> - * NOTE: vhci_dequeue() must be considered carefully. When shutdowning
> + * NOTE: vhci_dequeue() must be considered carefully. When shuting down
Shutting.
WBR, Sergei
prev parent reply other threads:[~2012-07-30 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 14:23 [PATCH]staging: usbip: Fix typos Justin P. Mattock
2012-07-30 16:34 ` Sergei Shtylyov [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=5016B7B3.2040702@mvista.com \
--to=sshtylyov@mvista.com \
--cc=gregkh@linuxfoundation.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mfm@muteddisk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.