From: Jesper Juhl <jesper.juhl@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: pcaudio@crystal.cirrus.com, twoller@crystal.cirrus.com,
Jaroslav Kysela <perex@suse.cz>, Alan Cox <alan@redhat.com>,
Nils Faerber <nils@kernelconcepts.de>,
Andrew Morton <akpm@osdl.org>,
Jesper Juhl <jesper.juhl@gmail.com>
Subject: [PATCH] OSS: cs46xx cleanup and tiny bugfix
Date: Thu, 20 Apr 2006 23:39:43 +0200 [thread overview]
Message-ID: <200604202339.43319.jesper.juhl@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Here's a patch for cs46xx that
- (mostly) cleans up the cs46xx driver according to CodingStyle
- removes a bunch of pointless casts
- fixes a small, potential use of uninitialized variable, bug
- reduces the size of the compiled code by 36 bytes
- reduces the size of the source file by 1831 bytes
I know I should probably have split this into bits, but since I only
thought of that *after* doing all the edits, splitting it up would have
been a royal pain. And since these are all pretty trivial changes I thought
I'd just submit the one huge patch and hope people could live with it (if
not, then just tell me and I'll split it).
The bug fix that's in there may be hard to spot, so I'll point it out. It's
the
- int val, valsave, mapped, ret;
+ int val, valsave, ret;
+ int mapped = 0;
bit.
Without that change we may use `mapped' uninitialized if, in cs_ioctl, the
first test of "if(state)" is false and the second "if(state)" test is true.
Patch is compile tested.
Due to the size of the patch (98838 bytes) I'm not including it inline in
this email, but have instead attached it as a bzip2 compressed file.
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
sound/oss/cs46xx.c | 1272 ++++++++++++++++++++---------------------------------
1 files changed, 489 insertions(+), 783 deletions(-)
[-- Attachment #2: cs46xx-cleanup.patch.bz2 --]
[-- Type: application/x-bzip2, Size: 17884 bytes --]
reply other threads:[~2006-04-20 21:39 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=200604202339.43319.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nils@kernelconcepts.de \
--cc=pcaudio@crystal.cirrus.com \
--cc=perex@suse.cz \
--cc=twoller@crystal.cirrus.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
all inboxes | Powered by JetHome®