public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org,
	"Justin P. Mattock" <justinmattock@gmail.com>
Subject: [PATCH 5/5]NEXT:drivers:staging:quatech_usb2:quatech_usb2.c Fix typo in staging:quatech_usb2
Date: Mon, 19 Mar 2012 08:17:53 -0700	[thread overview]
Message-ID: <1332170273-3482-5-git-send-email-justinmattock@gmail.com> (raw)
In-Reply-To: <1332170273-3482-1-git-send-email-justinmattock@gmail.com>

From: "Justin P. Mattock" <justinmattock@gmail.com>

The below patch fixes a typo that I found while reading.

Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>

---
 drivers/staging/quatech_usb2/quatech_usb2.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/staging/quatech_usb2/quatech_usb2.c b/drivers/staging/quatech_usb2/quatech_usb2.c
index bb977e0..cb7d906 100644
--- a/drivers/staging/quatech_usb2/quatech_usb2.c
+++ b/drivers/staging/quatech_usb2/quatech_usb2.c
@@ -732,7 +732,7 @@ static int qt2_write(struct tty_struct *tty, struct usb_serial_port *port,
 	}
 
 	/* We must fill the first 5 bytes of anything we sent with a transmit
-	 * header which directes the data to the correct port. The maximum
+	 * header which directs the data to the correct port. The maximum
 	 * size we can send out in one URB is port->bulk_out_size, which caps
 	 * the number of bytes of real data we can send in each write. As the
 	 * semantics of write allow us to write less than we were give, we cap
-- 
1.7.5.4


  parent reply	other threads:[~2012-03-19 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 15:17 [PATCH 1/5]NEXT:drivers:staging:nvec:nvec.h Fix typos in staging:nvec Justin P. Mattock
2012-03-19 15:17 ` [PATCH 2/5]NEXT:drivers:staging:ozwpan:ozhcd.c Fix typos in staging:ozwpan Justin P. Mattock
2012-03-19 15:27   ` Chris Kelly
2012-03-19 15:17 ` [PATCH 3/5]NEXT:drivers:staging:olpc_dcon:olpc_dcon_xo_1.c Fix typo in staging:olpc_dcon Justin P. Mattock
2012-03-19 15:17 ` [PATCH 4/5]NEXT:drivers:staging:panel:panel.c Fix typo in staging:panel Justin P. Mattock
2012-03-19 15:17 ` Justin P. Mattock [this message]
2012-03-26 14:29 ` [PATCH 1/5]NEXT:drivers:staging:nvec:nvec.h Fix typos in staging:nvec Justin P. Mattock
2012-03-26 14:48   ` Greg KH
2012-03-26 15:00     ` Justin P. Mattock
2012-03-26 16:42 ` Julian Andres Klode

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=1332170273-3482-5-git-send-email-justinmattock@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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