From: Alexey Dobriyan <adobriyan@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
kirk@braille.uwo.ca, linux-kernel@vger.kernel.org,
speakup@braille.uwo.ca, gregkh@suse.de
Subject: Re: 2.6.13-rc2-mm1: some speakup nitpicks
Date: Sat, 9 Jul 2005 17:16:21 +0400 [thread overview]
Message-ID: <200507091716.22334.adobriyan@gmail.com> (raw)
In-Reply-To: <20050709020717.GQ3671@stusta.de>
On Saturday 09 July 2005 06:07, Adrian Bunk wrote:
> - SPEAKUP_DEFAULT shouldn't be asked if SPEAKUP=n
> - "make namespacecheck" shows tons of needlessly global code
> - the static variable special_handler is EXPORT_SYMBOL'ed
> - #define MIN should be removed
> - the file cvsversion.h only for keeping a CVS date is a bit
> overkill
> - spk_con_module.h is not exactly how we use header files in the kernel
> - many of the #ifdef MODULE's point to things that could be done better
> (especially the #include "mod_code.c"'s)
> - the things in synthlist.h could be done less ugly
> - speakupconf is a userspace script that belongs under Documentation/
> - dtload.c is not kernel code, and should therefore not be in that
> directory
> - the code should follow Documentation/CodingStyle better
> (no spaces between the braces and function arguments)
> - building speakup_keyhelp.c modular even in a kernel that doesn't
> support modules is silly
> - #include <linux/...> belongs before #include <asm/...>
- Plenty, plenty of sparse warnings.
- #define PROC_READ_PROTOTYPE char *page, char **start, off_t off, \
int count, int *eof, void *data
#define PROC_WRITE_PROTOTYPE struct file *file, const char *buffer, \
u_long count, void *data
- #define CAP_A 'A'
#define CAP_Z 'Z'
and other fun in drivers/char/speakup/spk_priv.h
- LINUX_VERSION_CODE ifdeffery
next prev parent reply other threads:[~2005-07-09 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 11:00 2.6.13-rc2-mm1 Andrew Morton
2005-07-07 11:27 ` 2.6.13-rc2-mm1 Miklos Szeredi
2005-07-07 11:34 ` 2.6.13-rc2-mm1 Andrew Morton
2005-07-07 11:44 ` 2.6.13-rc2-mm1 Miklos Szeredi
2005-07-07 11:32 ` 2.6.13-rc2-mm1 Brice Goglin
2005-07-07 11:42 ` 2.6.13-rc2-mm1 Andrew Morton
2005-07-07 11:44 ` 2.6.13-rc2-mm1 Brice Goglin
2005-07-07 12:46 ` 2.6.13-rc2-mm1 Michael Krufky
2005-07-07 14:19 ` 2.6.13-rc2-mm1 Robert Love
2005-07-07 16:14 ` 2.6.13-rc2-mm1 Roland Dreier
2005-07-09 2:07 ` 2.6.13-rc2-mm1: some speakup nitpicks Adrian Bunk
2005-07-09 3:02 ` Greg KH
2005-07-09 13:16 ` Alexey Dobriyan [this message]
2005-07-11 16:29 ` 2.6.13-rc2-mm1 - unknown symbol: is_broadcast_ether_addr Damir Perisa
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=200507091716.22334.adobriyan@gmail.com \
--to=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=kirk@braille.uwo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=speakup@braille.uwo.ca \
/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