From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-kernel@vger.kernel.org
Subject: Re: __user annotations
Date: Sat, 7 Jun 2003 18:43:30 +0200 [thread overview]
Message-ID: <20030607164330.GA20312@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0306070917150.2840-100000@home.transmeta.com>
On Sat, Jun 07, 2003 at 09:25:43AM -0700, Linus Torvalds wrote:
>
> You can even have user pointers _inside_ the structure: because "sparse"
Since we start to know your checker by the name sparse, why not
call the default executable sparse?
Sam
===== Makefile 1.21 vs edited =====
--- 1.21/Makefile Tue Jun 3 03:15:27 2003
+++ edited/Makefile Sat Jun 7 18:41:15 2003
@@ -2,7 +2,7 @@
CFLAGS=-g -Wall
AR=ar
-PROGRAMS=test-lexing test-parsing obfuscate check
+PROGRAMS=test-lexing test-parsing obfuscate sparse
LIB_H= token.h parse.h lib.h symbol.h scope.h expression.h target.h
@@ -22,7 +22,7 @@
obfuscate: obfuscate.o $(LIB_FILE)
gcc -o $@ $< $(LIB_FILE)
-check: check.o $(LIB_FILE)
+sparse: check.o $(LIB_FILE)
gcc -o $@ $< $(LIB_FILE)
$(LIB_FILE): $(LIB_OBJS)
next prev parent reply other threads:[~2003-06-07 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 21:34 [CHECKER][PATCH] awe_wave.c user pointer dereference Hollis Blanchard
2003-06-05 22:07 ` Linus Torvalds
2003-06-06 16:46 ` __user annotations Hollis Blanchard
2003-06-06 17:28 ` Linus Torvalds
2003-06-07 0:32 ` Paul Mackerras
2003-06-07 0:42 ` Sam Ravnborg
2003-06-07 0:52 ` Paul Mackerras
2003-06-07 0:43 ` Linus Torvalds
2003-06-07 1:06 ` Arnaldo Carvalho de Melo
2003-06-07 1:09 ` Paul Mackerras
2003-06-07 16:49 ` Daniel Jacobowitz
2003-06-08 2:17 ` Paul Mackerras
2003-06-07 12:32 ` Ingo Oeser
2003-06-07 16:25 ` Linus Torvalds
2003-06-07 16:43 ` Sam Ravnborg [this message]
2003-06-07 16:48 ` Sam Ravnborg
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=20030607164330.GA20312@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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®