From: Timothy Miller <miller@techsource.com>
To: Valdis.Kletnieks@vt.edu
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Can one build 2.5.68 with allyesconfig?
Date: Tue, 22 Apr 2003 18:25:37 -0400 [thread overview]
Message-ID: <3EA5C161.9060104@techsource.com> (raw)
In-Reply-To: 200304222057.h3MKvbLq005110@turing-police.cc.vt.edu
Valdis.Kletnieks@vt.edu wrote:
>On Tue, 22 Apr 2003 17:04:34 EDT, Timothy Miller said:
>
>
>
>
>'make -k' should suffice there. I assume you're grovelling them out of
>the .o files? Otherwise, just grepping the *.c should be OK.
>
Scanning .o files gets things which are not printk format strings.
Grepping .c files doesn't get macros. The only choice is to produce .i
files.
>
>Also, note that you probably want to *also* do an 'allmodconfig' just in
>case there's printk inside a #ifdef MODULE....
>
>
What will get the greater coverage? There seem to be some things that
don't get 'y' or 'm' in .config when you do an allmodconfig.
next prev parent reply other threads:[~2003-04-22 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 20:49 Can one build 2.5.68 with allyesconfig? Timothy Miller
2003-04-22 20:41 ` Valdis.Kletnieks
2003-04-22 20:51 ` Randy.Dunlap
2003-04-22 21:04 ` Timothy Miller
2003-04-22 20:57 ` Valdis.Kletnieks
2003-04-22 22:25 ` Timothy Miller [this message]
2003-04-22 21:06 ` Richard B. Johnson
2003-04-23 19:52 ` John Cherry
2003-04-23 20:48 ` Jörn Engel
2003-04-24 0:01 ` John Cherry
2003-04-24 9:26 ` Jörn Engel
2003-04-22 21:08 ` Sam Ravnborg
2003-04-22 21:19 ` Randy.Dunlap
2003-04-23 11:58 ` Jörn Engel
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=3EA5C161.9060104@techsource.com \
--to=miller@techsource.com \
--cc=Valdis.Kletnieks@vt.edu \
--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 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.