From: "David S. Miller" <davem@redhat.com>
To: Jirka Kosina <jikos@jikos.cz>
Cc: linux-kernel@vger.kernel.org, pekkas@netcore.fi
Subject: Re: [PATCH] IPv6 can't be built as module additionally
Date: Thu, 20 May 2004 15:50:42 -0700 [thread overview]
Message-ID: <20040520155042.223b05e3.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0405210007240.25914@twin.jikos.cz>
On Fri, 21 May 2004 00:16:06 +0200 (CEST)
Jirka Kosina <jikos@jikos.cz> wrote:
> This is because ipv6-specific functions in drivers/char/random.c
> are inside #ifdefs, and as random.c is almost always built directly into
> kernel, recompilation of whole kernel can't be avoided.
This is the smallest problem, several main kernel data structures
change size based upon whether ipv6 has been enabled in any way
or not.
So even with your patch, compiling ipv6 outside of the kernel will
still not work even though it might build.
This has been discussed to death in the past I do believe :-)
next prev parent reply other threads:[~2004-05-20 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 22:16 [PATCH] IPv6 can't be built as module additionally Jirka Kosina
2004-05-20 22:50 ` David S. Miller [this message]
2004-05-20 23:30 ` Andy Isaacson
2004-05-20 23:37 ` David S. Miller
2004-05-21 23:36 ` Valdis.Kletnieks
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=20040520155042.223b05e3.davem@redhat.com \
--to=davem@redhat.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pekkas@netcore.fi \
/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