From: Magnus Damm <magnus.damm@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] disable builtin modules
Date: Sun, 20 Mar 2005 11:53:42 +0100 [thread overview]
Message-ID: <aec7e5c3050320025323257b20@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503201049190.24849@yvahk01.tjqt.qr>
On Sun, 20 Mar 2005 10:51:41 +0100 (MET), Jan Engelhardt
<jengelh@linux01.gwdg.de> wrote:
>
> >This patch makes it possible to disable built in code from the kernel
> >command line. The patch is rather simple - it extends the compiled-in case
> >of module_init() to include __setup() with a name based on KBUILD_MODNAME.
>
> What if there is already an option like the modname? I do not know of any
> code that currently does so, but you never know.
>
> Are acpi= and apm= already what your patch wants to extend to other modules?
> If not, there's conflict.
There is a conflict. Thanks for pointing that out.
Both the obsolete __setup() parameter code and the module parameter
code in kernel/params.c are limited to a single matching parameter.
The first matching parameter will be used, and non-early obsoleted
parameters are overridden by module parameter code. If I understand
the code correctly that is. =)
Maybe it is possible to (mis)use early_param instead of __setup and
let these parameters become "high priority" parameters that only are
parsed by do_early_param()...?
/ magnus
prev parent reply other threads:[~2005-03-20 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 23:34 [PATCH] disable builtin modules Magnus Damm
2005-03-20 9:51 ` Jan Engelhardt
2005-03-20 10:53 ` Magnus Damm [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=aec7e5c3050320025323257b20@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.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