From: "Riley Williams" <rhw@@MemAlpha.cx>
To: "Eric S Raymond" <esr@thyrsus.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: OK, let's try cleaning up another nit. Is anyone paying attention?
Date: Sun, 29 Jul 2001 11:47:00 +0100 [thread overview]
Message-ID: <00e101c1181b$e1c43380$5ffca8c0@UFP.CX> (raw)
In-Reply-To: <E14qaeC-0001DZ-00@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
Hi Alan, Eric.
>> That's the main thing I'm after right now -- I want to cut down on
>> the false positives in my orphaned-symbol reports so that the
actual
>> bugs will stand out.
> Teach it to read a 'symbolstoignore' file.
>
> Part of the problem you are hitting right now is that most
architectures are
> not yet fully in sync with 2.4 nor likely to all be for another few
iterations.
Not sure if it's relevant, but, I've enclosed (1) a bash script that
produces an analysis of the CONFIG_ variables in a specified Linux
kernel source tree, and (2) the results from running that on the 2.4.5
tree. It analyses all files matching '*.?' and '[Cc]onfig.in' in the
specified tree, and reports on the results by summarising both how
many times each CONFIG_* variable is used total, which files it is
used in, and how many times it is used in each file.
Best wishes from Riley.
[-- Attachment #2: allgrep.gz --]
[-- Type: application/octet-stream, Size: 477 bytes --]
next prev parent reply other threads:[~2001-07-29 10:48 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 2:36 OK, let's try cleaning up another nit. Is anyone paying attention? Matthew Wilcox
2001-04-20 3:00 ` Eric S. Raymond
2001-04-20 3:17 ` Matthew Wilcox
2001-04-20 4:07 ` james rich
2001-04-20 4:19 ` Matthew Wilcox
2001-04-20 4:52 ` Albert D. Cahalan
2001-04-20 5:17 ` Rik van Riel
2001-04-20 13:13 ` [parisc-linux] " Alan Cox
2001-04-20 13:35 ` Eric S. Raymond
2001-04-20 13:43 ` Alan Cox
2001-04-20 13:53 ` Eric S. Raymond
2001-04-20 14:03 ` Alan Cox
2001-04-20 14:19 ` Eric S. Raymond
2001-04-20 14:44 ` Alan Cox
2001-04-20 14:59 ` Eric S. Raymond
2001-04-20 15:51 ` Tom Rini
2001-04-20 16:06 ` Jeff Garzik
2001-04-20 16:15 ` Bob McElrath
2001-04-20 16:21 ` Matthew Wilcox
2001-04-20 19:00 ` Jeff Dike
2001-04-20 18:47 ` Matthew Wilcox
2001-04-20 21:55 ` Jeff Dike
2001-04-20 18:53 ` Jes Sorensen
2001-04-20 16:26 ` Jeff Garzik
2001-04-20 16:35 ` Nicolas Pitre
2001-04-20 16:50 ` Eric S. Raymond
2001-04-20 19:08 ` Russell King
2001-04-21 3:08 ` Tom Leete
2001-04-21 8:53 ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone rmk
2001-04-20 18:20 ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? Tom Rini
2001-04-20 18:48 ` Nicolas Pitre
2001-04-20 18:55 ` Tom Rini
2001-04-20 21:19 ` David Woodhouse
2001-04-20 21:24 ` Eric S. Raymond
2001-04-20 21:29 ` David Woodhouse
2001-04-20 21:35 ` Eric S. Raymond
2001-04-20 22:53 ` Alan Cox
2001-04-21 0:37 ` Eric S. Raymond
2001-04-21 23:39 ` Jes Sorensen
2001-04-21 12:32 ` David Woodhouse
2001-04-23 21:12 ` [patch] fix broken symbols (was Re: OK, let's try ...) Arjan van de Ven
2001-04-20 21:39 ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? David Woodhouse
2001-04-21 0:24 ` Eric S. Raymond
2001-04-20 18:50 ` Russell King
2001-04-20 21:23 ` Andreas Dilger
2001-04-21 0:52 ` Proposal for better attribution structure Eric S. Raymond
2001-04-20 8:19 ` OK, let's try cleaning up another nit. Is anyone paying attention? David Woodhouse
2001-04-20 19:47 ` Eric S. Raymond
2001-04-20 20:00 ` Matthew Wilcox
2001-04-20 20:13 ` Eric S. Raymond
2001-04-20 20:55 ` Alan Cox
2001-04-21 6:48 ` [parisc-linux] " Grant Grundler
2001-04-21 14:52 ` Eric S. Raymond
2001-04-20 13:08 ` Alan Cox
2001-04-20 13:18 ` Eric S. Raymond
2001-07-29 10:47 ` Riley Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 22:50 Eric S. Raymond
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='00e101c1181b$e1c43380$5ffca8c0@UFP.CX' \
--to=esr@thyrsus.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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