From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
davej@redhat.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: __init dependencies
Date: Mon, 11 Oct 2004 21:04:46 -0700 [thread overview]
Message-ID: <416B57DE.4070605@osdl.org> (raw)
In-Reply-To: <416ADC63.6010709@osdl.org>
Randy.Dunlap wrote:
> Andrew Morton wrote:
>
>> Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>>
>>> I guess it's about time for a tool to autodetect __init dependencies?
>>
>>
>>
>> `make buildcheck' does this. Looks like nobody is using it.
>
>
> I have asked that one of the forever-building machines here (OSDL)
> do that.
> I'll get back to that request....
John Cherry has been running 'make buildcheck' regularly,
but apparently nobody has been looking.
Latest (2.6.9-rc4) is here:
http://developer.osdl.org/cherry/compile/2.6/linux-2.6.9-rc4.results/2.6.9-rc4.reference_init26.bzImage.txt
My experience with output of buildcheck is that it's verbose and has
lots of false positives. (Yes, I have used it and generated patches
from it.) First thing I do is delete all lines that match
"data.*init" or "data.*exit". These are (usually -- famous word) OK.
Then someone can look at the entries that really need to be checked,
such as this list, derived from the larger list above:
http://developer.osdl.org/rddunlap/doc/2.6.9-rc4.reference_init26.bzImage.txt
I'll look over it in the next few days.
--
~Randy
next prev parent reply other threads:[~2004-10-12 4:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 22:57 [PATCH] find_isa_irq_pin can't be __init Dave Jones
2004-10-11 11:33 ` __init dependencies (was: Re: [PATCH] find_isa_irq_pin can't be )__init Geert Uytterhoeven
2004-10-11 19:12 ` Andrew Morton
2004-10-11 19:16 ` Dave Jones
2004-10-11 19:17 ` __init dependencies Randy.Dunlap
2004-10-12 4:04 ` Randy.Dunlap [this message]
2004-10-12 4:19 ` Andrew Morton
2004-10-12 6:06 ` Keith Owens
2004-10-20 16:08 ` [PATCH] __init dependencies: ignore __param Randy.Dunlap
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=416B57DE.4070605@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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