From: Martin Dalecki <dalecki@evision-ventures.com>
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 02:01:27 +0200 [thread overview]
Message-ID: <3CD1D357.4050906@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205022054160.8024-100000@conn6m.toms.net>
Uz.ytkownik Tom Oehser napisa?:
>>Tom Oehser <tom@toms.net> wrote:
>>
>>>Changing all =m to =n in my config makes a 4K difference in the kernel size.
>>
>
> On Fri, 3 May 2002, Keith Owens wrote:
>
>
>>The majority of modules have no effect on kernel size but some modules
>>require base kernel code as well. This is typically common code or low
>>level setup functions. You will find that those modules will not load
>>now or will break.
>
>
> Great. I must have missed the list of exactly *which* modules do this...
>
> Any ideas on a reasonable way of how to identify them?
Please grep for EXPORT_SYMBOL().
next prev parent reply other threads:[~2002-05-03 1:04 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 [this message]
2002-05-03 1:28 ` Keith Owens
2002-05-03 15:03 ` David Woodhouse
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=3CD1D357.4050906@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox