From: David Woodhouse <dwmw2@infradead.org>
To: Tom Oehser <tom@toms.net>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: module choices affecting base kernel size???
Date: Fri, 03 May 2002 16:03:39 +0100 [thread overview]
Message-ID: <11194.1020438219@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205022054160.8024-100000@conn6m.toms.net>
tom@toms.net said:
> Any ideas on a reasonable way of how to identify them?
A recursive grep for #if.*CONFIG_.*MODULE should find the majority of
offending code. As Keith says, some of it is in the Makefiles, but the
majority is in the code.
--
dwmw2
prev parent reply other threads:[~2002-05-03 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 14:49 module choices affecting base kernel size??? Tom Oehser
2002-05-02 23:58 ` Keith Owens
2002-05-03 0:57 ` Tom Oehser
2002-05-03 0:01 ` Martin Dalecki
2002-05-03 1:28 ` Keith Owens
2002-05-03 15:03 ` David Woodhouse [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=11194.1020438219@redhat.com \
--to=dwmw2@infradead.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@toms.net \
/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.