From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@linux-speakup.org
Subject: Fwd: Re: speakup issues
Date: Thu, 9 May 2013 18:49:15 -0500 [thread overview]
Message-ID: <20130509234915.GB2123@linux1> (raw)
----- Forwarded message from Dan Carpenter <dan.carpenter@oracle.com> -----
> Date: Thu, 9 May 2013 21:55:26 +0300
> From: Dan Carpenter <dan.carpenter@oracle.com>
> To: William Hubbs <w.d.hubbs@gmail.com>
> Cc: gregkh@suse.de, devel@driverdev.osuosl.org
> Subject: Re: speakup issues
>
> It's like every function in speakup has something that's just a
> little bit ugly about it.
>
> For example
> 1) No spaces around operations. IE "if (x&4) {" vs "if (x & 4) {".
> 2) No blank lines between the variable declarations and the code.
> 3) The 'E' in E_DEFAULT stands for "enum" which is bogus.
> 4) Custom macros like spk_lock()
> 5) Using u_char instead of u8. (Yes, there are thousands of places
> in the kernel which do this but it's mostly horrid legacy code
> like ISDN).
> 6) In synth_direct_store() the last 5 bytes of the tmp[] buf are not
> used.
> 7) Unnecessary casts.
> 8) Things like this:
>
> char *cp;
> u_char *cp1;
>
> "cp1" is a poorly chosen variable name.
>
> Anyway, there is a lot of stuff. It just needs someone to go
> through it bit by bit and re-write it cleaner.
>
> regards,
> dan carpenter
>
----- End forwarded message -----
next reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
William Hubbs [this message]
William Hubbs
William Hubbs
` covici
` Jason White
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=20130509234915.GB2123@linux1 \
--to=w.d.hubbs@gmail.com \
--cc=speakup@linux-speakup.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).