From: Jesper Juhl <juhl@eisenstein.dk>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] pedantic code cleanup - am I wasting my time with this?
Date: Mon, 23 Apr 2001 17:26:27 +0200 [thread overview]
Message-ID: <3AE449A3.3050601@eisenstein.dk> (raw)
Hi people,
I'm reading through various pieces of source code to try and get an
understanding of how the kernel works (with the hope that I'll
eventually be able to contribute something really usefull, but you've
got to start somewhere ;)
While reading through the source I've stumbled across various bits and
pieces that are not exactely wrong, but not strictly correct either. I
was wondering if I would be wasting my time by cleaning this up or if it
would actually be appreciated. One example of these things is the patch
below:
--- linux-2.4.3-vanilla/include/linux/rtnetlink.h Sun Apr 22
02:29:20 2001
+++ linux-2.4.3/include/linux/rtnetlink.h Mon Apr 23 17:09:02 2001
@@ -112,7 +112,7 @@
RTN_PROHIBIT, /* Administratively prohibited */
RTN_THROW, /* Not in this table */
RTN_NAT, /* Translate this address */
- RTN_XRESOLVE, /* Use external resolver */
+ RTN_XRESOLVE /* Use external resolver */
};
#define RTN_MAX RTN_XRESOLVE
@@ -278,7 +278,7 @@
#define RTAX_CWND RTAX_CWND
RTAX_ADVMSS,
#define RTAX_ADVMSS RTAX_ADVMSS
- RTAX_REORDERING,
+ RTAX_REORDERING
#define RTAX_REORDERING RTAX_REORDERING
};
@@ -501,7 +501,7 @@
TCA_OPTIONS,
TCA_STATS,
TCA_XSTATS,
- TCA_RATE,
+ TCA_RATE
};
#define TCA_MAX TCA_RATE
All the above does is to remove the last comma from 3 enumeration lists.
I know that gcc has no problem with that, but to be strictly correct the
last entry should not have a trailing comma.
Another example is the following line (1266) from linux/include/net/sock.h
return (waitall ? len : min(sk->rcvlowat, len)) ? : 1;
To be strictly correct the second expression (between '?' and ':' )
should not be omitted (all you guys already know that ofcourse).
Would patches that clean up stuff like that be appreciated or am I just
wasting my time?
Should I just adopt an 'if gcc -Wall does not complain then it's ok'
attitude and leave this stuff alone?
Best regards,
Jesper Juhl - juhl@eisenstein.dk
next reply other threads:[~2001-04-23 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 15:26 Jesper Juhl [this message]
2001-04-23 15:24 ` [PATCH] pedantic code cleanup - am I wasting my time with this? Jeff Garzik
2001-04-23 15:37 ` Richard Gooch
2001-04-23 16:23 ` Jesper Juhl
2001-04-23 15:48 ` Sean Hunter
2001-04-23 15:58 ` Jesper Juhl
2001-04-24 4:59 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 8:25 Stephen Satchell
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=3AE449A3.3050601@eisenstein.dk \
--to=juhl@eisenstein.dk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox