From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: "Andy Whitcroft" <apw@shadowen.org>,
"Andrew Morton" <akpm@osdl.org>,
"Randy Dunlap" <rdunlap@xenotime.net>,
"Joel Schopp" <jschopp@austin.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update checkpatch.pl to version 0.03
Date: Thu, 7 Jun 2007 16:39:35 +0200 [thread overview]
Message-ID: <9a8748490706070739l14dbebb0s87d6cfe6bd93b164@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706071622280.8762@fbirervta.pbzchgretzou.qr>
On 07/06/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Jun 6 2007 11:05, Jesper Juhl wrote:
> >
> > - Source files should be 7bit ASCII
>
> Nah. Think of....
>
> MODULE_AUTHOR("J. Ørsted <jorsted@foobar.com>");
>
That's true. I wrote that comment shortly after reading
http://lkml.org/lkml/2007/6/4/448 , but you are right, 7bit ASCII can
be too limiting at times... Hmmm...
> > - Maybe warn about usage of float/double in source files?
>
> Generally yes, maybe, but see arch/i386/kernel/cpu/bugs.c,
> arch/i386/math-emu/. Generally there is nothing to it. I think the
> feature to allow the kernel to use [i387] FP without manually
> saving/restoring the FP stack has been added some time ago.
>
I know there are places where floats and doubles can be used safely,
but for those rare occasions wouldn't it make sense to have the script
warn and require the submitter to justify the use? After all, the
general rule is to not use floating point in the kernel, so such a
patch is suspicious.
> > - 'return' is not a function, so warn about patches that think it is
> > and use 'return(expr);' (this one is tricky since 'return (expr);' can
> > be OK in some cases.
>
> Now, if we could detect superfluous parentheses and branches,
> that'd be cool ;-) there are too many if ((a < 5) || (b > 6)) around.
>
Yeah wouldn't it be cool :-) It might require a bit too much perl
magic to actually implement something sane, but I just threw every
idea that came into my mind into the mail, assuming Andy could sort
out the ones that were a little too crazy ;)
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2007-06-07 14:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 9:46 Andy Whitcroft
2007-06-04 9:55 ` [PATCH] update feature-removal-schedule.txt to include deprecated functions Andy Whitcroft
2007-06-04 15:49 ` [PATCH] update checkpatch.pl to version 0.03 jschopp
2007-06-04 16:51 ` Andy Whitcroft
2007-06-04 17:22 ` jschopp
2007-06-05 18:45 ` Andy Whitcroft
2007-06-05 9:56 ` Andy Whitcroft
2007-06-04 16:25 ` Jan Engelhardt
2007-06-04 18:41 ` Andrew Morton
2007-06-04 19:08 ` Andy Whitcroft
2007-06-04 19:08 ` Rene Herman
2007-06-04 20:04 ` Randy Dunlap
2007-06-05 18:39 ` Andy Whitcroft
2007-06-08 9:31 ` Andy Whitcroft
2007-06-08 10:08 ` Rene Herman
2007-06-05 8:14 ` Heiko Carstens
2007-06-06 9:05 ` Jesper Juhl
2007-06-07 14:28 ` Jan Engelhardt
2007-06-07 14:39 ` Jesper Juhl [this message]
2007-06-07 19:34 ` Adrian Bunk
2007-06-07 22:22 ` Alan Cox
2007-06-07 23:21 ` Adrian Bunk
2007-06-07 23:41 ` Alan Cox
2007-06-08 0:04 ` Adrian Bunk
2007-06-08 4:37 ` Jon Masters
2007-06-08 8:58 ` Jan-Benedict Glaw
2007-06-08 10:52 ` Alan Cox
2007-06-08 12:39 ` Adrian Bunk
2007-06-08 14:34 ` Jesper Juhl
2007-06-08 14:42 ` Adrian Bunk
2007-06-08 15:16 ` Jan Engelhardt
2007-06-08 15:37 ` Jon Masters
2007-06-08 15:42 ` Alan Cox
2007-06-08 16:39 ` Adrian Bunk
2007-06-08 18:43 ` Jan Engelhardt
2007-06-08 16:03 ` Roland Dreier
2007-06-07 23:49 ` Adrian Bunk
2007-06-07 19:32 ` Adrian Bunk
2007-06-07 22:18 ` Alan Cox
2007-06-06 11:49 ` Jesper Juhl
2007-06-07 11:46 ` Andy Whitcroft
2007-06-07 11:52 ` Jesper Juhl
2007-06-07 15:16 ` checkpatch.pl: should be executable Andy Whitcroft
2007-06-07 15:33 ` jschopp
2007-06-07 14:22 ` [PATCH] update checkpatch.pl to version 0.03 Jan Engelhardt
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=9a8748490706070739l14dbebb0s87d6cfe6bd93b164@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=jengelh@computergmbh.de \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®