From: Walt Feasel <waltfeasel@gmail.com>
To: speakup@linux-speakup.org
Cc: w.d.hubbs@gmail.com, chris@the-brannons.com, kirk@braille.uwo.ca,
samuel.thibault@ens-lyon.org, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Walt Feasel <waltfeasel@gmail.com>
Subject: [PATCH] [STYLE]staging:speakup:speakup_dtlk.h Modify block comments
Date: Fri, 11 Nov 2016 20:13:54 -0500 [thread overview]
Message-ID: <1478913234-23858-1-git-send-email-waltfeasel@gmail.com> (raw)
Made suggested modifications from checkpatch in reference
to WARNING: Block comments should align the * on each line
Modified block text alignment for consistency
Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
---
drivers/staging/speakup/speakup_dtlk.h | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/speakup/speakup_dtlk.h b/drivers/staging/speakup/speakup_dtlk.h
index 46d885f..4dbbbe5 100644
--- a/drivers/staging/speakup/speakup_dtlk.h
+++ b/drivers/staging/speakup/speakup_dtlk.h
@@ -1,8 +1,8 @@
/* speakup_dtlk.h - header file for speakups DoubleTalk driver. */
#define SYNTH_IO_EXTENT 0x02
-#define SYNTH_CLEAR 0x18 /* stops speech */
- /* TTS Port Status Flags */
+#define SYNTH_CLEAR 0x18 /* stops speech */
+ /* TTS Port Status Flags */
#define TTS_READABLE 0x80 /* mask for bit which is nonzero if a
* byte can be read from the TTS port
*/
@@ -23,12 +23,12 @@
* writing, and goes 1 again 180-190
* 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.
- */
+#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.
+ */
#define TTS_ALMOST_EMPTY 0x04 /* mask for AE bit: When set to 1,
* indicates that less than 300 bytes
* are remaining in DoubleTalk's input
--
2.1.4
reply other threads:[~2016-11-12 1:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1478913234-23858-1-git-send-email-waltfeasel@gmail.com \
--to=waltfeasel@gmail.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@braille.uwo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).