From: rossb <rossb@google.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
mm-commits@vger.kernel.org, akpm@google.com, sam@ravnborg.org
Subject: Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree
Date: Fri, 15 Sep 2006 19:04:30 -0400 [thread overview]
Message-ID: <d43160c70609151604pfe83b3nc130f2abc250baa6@mail.google.com> (raw)
In-Reply-To: <20060915154752.d7bdb8a0.rdunlap@xenotime.net>
On 9/15/06, Randy.Dunlap <rdunlap@xenotime.net> wrote:
> > In some ways this is a bit risky, because the .config which is used for
> > compiling kernel/configs.c isn't necessarily the same as the .config which was
> > used to build vmlinux.
>
> and that's why a module wasn't allowed.
> It's not worth the risk IMO.
It's not worth the risk for distributions or if you are tyring to
support people building their own kernels. But if you are in an
environment where you have enough control that you are not worried the
kernel and the module being built at separate times or with different
configs, then it's a nice compromise between convenience and memory
use.
Ross
next prev parent reply other threads:[~2006-09-15 23:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609152158.k8FLw7ud018089@shell0.pdx.osdl.net>
2006-09-15 22:47 ` Randy.Dunlap
2006-09-15 23:04 ` rossb [this message]
2006-09-15 23:11 ` Randy.Dunlap
2006-09-15 23:41 ` Andrew Morton
2006-09-16 0:14 ` Randy.Dunlap
2006-09-16 0:23 ` Olivier Galibert
2006-09-16 0:33 ` Adrian Bunk
2006-10-02 1:17 ` Randy Dunlap
2006-10-02 6:32 ` Olaf Hering
2006-09-16 11:47 ` Arjan van de Ven
2006-09-17 0:48 ` rossb
2006-09-17 1:13 ` Adrian Bunk
2006-10-02 7:08 Mikael Pettersson
2006-10-02 10:42 ` Olivier Galibert
2006-10-02 11:23 Mikael Pettersson
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=d43160c70609151604pfe83b3nc130f2abc250baa6@mail.google.com \
--to=rossb@google.com \
--cc=akpm@google.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®