From: Joe Perches <joe@perches.com>
To: Arushi <arushisinghal19971997@gmail.com>, w.d.hubbs@gmail.com
Cc: chris@the-brannons.com, kirk@reisers.ca,
samuel.thibault@ens-lyon.org, gregkh@linuxfoundation.org,
speakup@linux-speakup.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192e: Aligning the * on each line in block comments
Date: Wed, 01 Feb 2017 13:58:23 -0800 [thread overview]
Message-ID: <1485986303.22276.3.camel@perches.com> (raw)
In-Reply-To: <20170201215207.GA6173@arushi-HP-Pavilion-Notebook>
On Thu, 2017-02-02 at 03:22 +0530, Arushi wrote:
> This patch fixes the issue by aligning the * on each line in block comments.
[]
> diff --git a/drivers/staging/speakup/speakup_decpc.c b/drivers/staging/speakup/speakup_decpc.c
[]
> @@ -85,8 +85,8 @@
> #define CTRL_io_priority 0x0c00 /* change i/o priority */
> #define CTRL_free_mem 0x0d00 /* get free paragraphs on module */
> #define CTRL_get_lang 0x0e00 /* return bit mask of loaded
> - * languages
> - */
> + * languages
> + */
Not correct.
> diff --git a/drivers/staging/speakup/speakup_dtlk.h b/drivers/staging/speakup/speakup_dtlk.h
[]
> @@ -24,11 +24,11 @@
> * usec later.
> */
> #define TTS_ALMOST_FULL 0x08 /* mask for AF bit: When set to 1,
> - * indicates that less than 300 bytes
> - * are available in the TTS input
> - * buffer. AF is always 0 in the PCM,
> - * TGN and CVSD modes.
> - */
> + * indicates that less than 300 bytes
> + * are available in the TTS input
> + * buffer. AF is always 0 in the PCM,
> + * TGN and CVSD modes.
> + */
here too, etc...
next prev parent reply other threads:[~2017-02-01 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 21:52 [PATCH] staging: rtl8192e: Aligning the * on each line in block comments Arushi
2017-02-01 21:58 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-12 10:45 Arushi Singhal
2017-02-12 10:27 Arushi
2017-02-09 11:40 Arushi
2017-02-01 19:19 Arushi
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=1485986303.22276.3.camel@perches.com \
--to=joe@perches.com \
--cc=arushisinghal19971997@gmail.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.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.