From: Julian Andres Klode <jak@jak-linux.org>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
Marc Dietrich <marvin24@gmx.de>
Subject: Re: [PATCH 1/5]NEXT:drivers:staging:nvec:nvec.h Fix typos in staging:nvec
Date: Mon, 26 Mar 2012 18:42:50 +0200 [thread overview]
Message-ID: <20120326164250.GA21100@jak-linux.org> (raw)
In-Reply-To: <1332170273-3482-1-git-send-email-justinmattock@gmail.com>
On Mon, Mar 19, 2012 at 08:17:49AM -0700, Justin P. Mattock wrote:
> From: "Justin P. Mattock" <justinmattock@gmail.com>
>
> The below patch fixes a typo I found while reading.
>
> Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
> Cc: Julian Andres Klode <jak@jak-linux.org>
You could have CCed Marc Dietrich <marvin24@gmx.de> as well. He's
also listed in MAINTAINERS.
> ---
> drivers/staging/nvec/nvec.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/staging/nvec/nvec.h b/drivers/staging/nvec/nvec.h
> index a4c17b0..ba6ed8f 100644
> --- a/drivers/staging/nvec/nvec.h
> +++ b/drivers/staging/nvec/nvec.h
> @@ -42,7 +42,7 @@
> * enum nvec_event_size - The size of an event message
> * @NVEC_2BYTES: The message has one command byte and one data byte
> * @NVEC_3BYTES: The message has one command byte and two data bytes
> - * @NVEC_VAR_SIZE: The message has one command byte, one count byte, and as
> + * @NVEC_VAR_SIZE: The message has one command byte, one count byte, and has
> * up to as many bytes as the number in the count byte. The
> * maximum is 32
We can probably just drop the [h]as as well, right? That sounds a bit
better to me.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
prev parent reply other threads:[~2012-03-26 16:43 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 ` [PATCH 5/5]NEXT:drivers:staging:quatech_usb2:quatech_usb2.c Fix typo in staging:quatech_usb2 Justin P. Mattock
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 [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=20120326164250.GA21100@jak-linux.org \
--to=jak@jak-linux.org \
--cc=gregkh@linuxfoundation.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marvin24@gmx.de \
/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.