From: Andrea Gelmini <andrea.gelmini@gelma.net>
To: andrea.gelmini@gelma.net
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Randy Dunlap <rdunlap@xenotime.net>,
alsa-devel@alsa-project.org, linux-doc@vger.kernel.org
Subject: [PATCH 094/199] Documentation/sound/oss/ESS: Checkpatch cleanup
Date: Sun, 23 May 2010 21:52:44 +0200 [thread overview]
Message-ID: <1274644376-24176-2-git-send-email-andrea.gelmini@gelma.net> (raw)
In-Reply-To: <1274644376-24176-1-git-send-email-andrea.gelmini@gelma.net>
Documentation/sound/oss/ESS:4: ERROR: trailing whitespace
Documentation/sound/oss/ESS:15: ERROR: trailing whitespace
Signed-off-by: Andrea Gelmini <andrea.gelmini@gelma.net>
---
Documentation/sound/oss/ESS | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/sound/oss/ESS b/Documentation/sound/oss/ESS
index bba93b4..e21c21c 100644
--- a/Documentation/sound/oss/ESS
+++ b/Documentation/sound/oss/ESS
@@ -1,7 +1,7 @@
Documentation for the ESS AudioDrive chips
In 2.4 kernels the SoundBlaster driver not only tries to detect an ESS chip, it
-tries to detect the type of ESS chip too. The correct detection of the chip
+tries to detect the type of ESS chip too. The correct detection of the chip
doesn't always succeed however, so unless you use the kernel isapnp facilities
(and you chip is pnp capable) the default behaviour is 2.0 behaviour which
means: only detect ES688 and ES1688.
@@ -12,7 +12,7 @@ people who want to use their ESS for recording sound.
Every chip that's detected as a later-than-es1688 chip has a 6 bits logarithmic
master volume control.
-Every chip that's detected as a ES1887 now has Full Duplex support. Made a
+Every chip that's detected as a ES1887 now has Full Duplex support. Made a
little testprogram that shows that is works, haven't seen a real program that
needs this however.
--
1.7.1.251.gf80a2
next prev parent reply other threads:[~2010-05-23 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 19:52 [PATCH 092/199] Documentation/sound/oss/ALS: Checkpatch cleanup Andrea Gelmini
2010-05-23 19:52 ` Andrea Gelmini [this message]
2010-05-23 19:52 ` [PATCH 095/199] Documentation/sound/oss/MultiSound: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 096/199] Documentation/sound/oss/Opti: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 097/199] Documentation/sound/oss/PAS16: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 098/199] Documentation/sound/oss/PSS: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 099/199] Documentation/sound/oss/PSS-updates: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 100/199] Documentation/sound/oss/README.OSS: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 101/199] Documentation/sound/oss/README.modules: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 102/199] Documentation/sound/oss/README.ymfsb: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 103/199] Documentation/sound/oss/SoundPro: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 104/199] Documentation/sound/oss/Tropez+: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 106/199] Documentation/sound/oss/WaveArtist: " Andrea Gelmini
2010-05-23 19:52 ` [PATCH 107/199] Documentation/sound/oss/btaudio: " Andrea Gelmini
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=1274644376-24176-2-git-send-email-andrea.gelmini@gelma.net \
--to=andrea.gelmini@gelma.net \
--cc=alsa-devel@alsa-project.org \
--cc=linux-doc@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rdunlap@xenotime.net \
--cc=tiwai@suse.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 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).