From: devzero@web.de
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] janitor project: fix gcc 4 warnings
Date: Thu, 15 Feb 2007 19:34:55 +0000 [thread overview]
Message-ID: <1629018918@web.de> (raw)
In-Reply-To: <20041219190903.GA30192@muc.de>
Hello !
i recognized that there are still quite a reasonable number of warnings when i compile a kernel, especially with allmodconfig.
is there somebody systematically working on fixing those warnings being left over in kernel source ?
i´m really a newbie to kernel development and not really a good C programmer, but i`d like to try to help fix those warnings. maybe this will freshen up my programming skills a little bit.
btw - http://developer.osdl.org/cherry/compile/ seems to be very outdated - wouldn´t it be good to monitor the "warnings regression" between kernel releases?
whenever i compile a kernel, i move that window to my second screen and whenever gcc spits out a warning, this draws someone`s attention. leaving that feeling "uuuhhh, ohhh - there must be something wrong with the kernel...."
so, is this the right place to discuss such fixes ?
anybody to volunteer on systematically fixing those warnings ?
regards
roland
sysadmin
_______________________________________________________________________
Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc\x022222
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2007-02-15 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 19:09 [KJ] janitor project: fix gcc 4 warnings Andi Kleen
2004-12-19 19:47 ` Matthew Wilcox
2004-12-19 20:03 ` Andi Kleen
2004-12-19 21:00 ` Tobias Klauser
2004-12-20 0:13 ` Adrian Bunk
2004-12-20 7:10 ` Andi Kleen
2004-12-20 8:03 ` Andi Kleen
2004-12-20 8:04 ` Andi Kleen
2004-12-20 12:31 ` Arnd Bergmann
2004-12-22 16:44 ` Kovarththanan Rajaratnam
2005-02-07 23:14 ` Randy.Dunlap
2007-02-15 19:34 ` devzero [this message]
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=1629018918@web.de \
--to=devzero@web.de \
--cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.