From: Roel Kluin <12o3l@tiscali.nl>
To: kernel-janitors@vger.kernel.org
Subject: Re: script to find incorrect tests on unsigneds
Date: Wed, 23 Apr 2008 19:36:23 +0000 [thread overview]
Message-ID: <480F8FB7.9090006@tiscali.nl> (raw)
In-Reply-To: <4808C90A.5040600@tiscali.nl>
Julia Lawall wrote:
>> I noted you had more results in the same files. Is there a difference
>> in results when you remove the asterisks before the expression?
>
> Actually, I'm a little puzzled by your results. None of your files seem
> to be in my output (based on a check of a few examples), but that is
> normal because you consider many other types. But none of my files are in
> your output either. Did you just remove them to avoid being redundant, or
> is your rule overlooking the simple unsigned int case?
These are only the results with unsigned typedefs. I removed the previous.
of the unsigned and unsigned long there were few that were not in your
results.
> I might have gotten a few more examples because of using the options
> -all_includes -I ./include. The it takes into account more include files,
> and thus has a better chance of finding structure fields that have an
> unsigned int type. But that doesn't seem to account for the difference.
Ok, thanks, I'll try that too.
> julia
To answer your other question: I'm already posting patches for the ones that
should be fixed. Patches that fix things are always welcome.
Regards,
Roel Kluin
prev parent reply other threads:[~2008-04-23 19:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 16:15 script to find incorrect tests on unsigneds Roel Kluin
2008-04-18 19:08 ` Julia Lawall
2008-04-19 14:05 ` esp_scsi incorrect unsigned test Matthew Wilcox
2008-04-19 14:05 ` Matthew Wilcox
2008-04-19 14:16 ` James Bottomley
2008-04-19 14:16 ` James Bottomley
2008-04-20 0:59 ` David Miller
2008-04-20 0:59 ` David Miller
2008-04-19 14:17 ` u14-3f " Matthew Wilcox
2008-04-19 14:17 ` Matthew Wilcox
[not found] ` <Pine.LNX.4.64.0804182101200.14832-QfmoRoYWmW9knbxzx/v8hQ@public.gmane.org>
2008-04-19 14:24 ` script to find incorrect tests on unsigneds Matthew Wilcox
2008-04-19 14:24 ` Matthew Wilcox
2008-04-19 14:49 ` Matthew Wilcox
2008-04-19 14:49 ` Matthew Wilcox
2008-04-18 19:36 ` Julia Lawall
2008-04-19 13:29 ` walter harms
2008-04-19 13:43 ` Matthew Wilcox
2008-04-19 15:20 ` Julia Lawall
2008-04-19 15:43 ` Julia Lawall
2008-04-22 21:06 ` Julia Lawall
2008-04-22 21:28 ` Roel Kluin
2008-04-23 5:47 ` Julia Lawall
2008-04-23 9:26 ` Roel Kluin
2008-04-23 9:30 ` Roel Kluin
2008-04-23 9:54 ` Julia Lawall
2008-04-23 10:02 ` Julia Lawall
2008-04-23 10:26 ` Roel Kluin
2008-04-23 14:02 ` Roel Kluin
2008-04-23 14:05 ` Roel Kluin
2008-04-23 14:11 ` Roel Kluin
2008-04-23 14:24 ` Julia Lawall
2008-04-23 16:01 ` Roel Kluin
2008-04-23 17:59 ` Roel Kluin
2008-04-23 18:58 ` Julia Lawall
2008-04-23 19:12 ` Julia Lawall
2008-04-23 19:36 ` Roel Kluin [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=480F8FB7.9090006@tiscali.nl \
--to=12o3l@tiscali.nl \
--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.