From: Paul Bolle <pebolle@tiscali.nl>
To: Iulia Manda <iulia.manda21@gmail.com>
Cc: tim.bird@sonymobile.com, linux-kernel@vger.kernel.org,
josh@joshtriplett.org
Subject: Re: [PATCH 1/3] kernel: Add a new config option to remove command line parsing
Date: Tue, 19 May 2015 11:35:59 +0200 [thread overview]
Message-ID: <1432028159.9091.63.camel@x220> (raw)
In-Reply-To: <1431949832-13606-1-git-send-email-iulia.manda21@gmail.com>
On Mon, 2015-05-18 at 14:50 +0300, Iulia Manda wrote:
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> +config CMDLINE_PARSE
> + bool "Enable support for command line parsing"
> + default y
> + ---help---
> + With this option set to 'Y', kernel parameters, both the ones
> + passed at boot time and at compile time are parsed.
> +
> + If you say no here, all the kernel parameters' values will be set
> + to their defaults at compile time, in order to make constant
> + folding possible.
> +
> + Systems with no space constraints should leave this option set to
> + 'Y'.
This adds a x86 specific Kconfig option.
> --- a/include/linux/moduleparam.h
> +++ b/include/linux/moduleparam.h
> +#ifdef CONFIG_CMDLINE_PARSE
> /* Called on module insert or kernel boot */
> extern char *parse_args(const char *name,
> char *args,
> @@ -359,6 +360,19 @@ extern char *parse_args(const char *name,
> s16 level_max,
> int (*unknown)(char *param, char *val,
> const char *doing));
> +#else
> +static inline char *parse_args(const char *name,
> + char *args,
> + const struct kernel_param *params,
> + unsigned num,
> + s16 level_min,
> + s16 level_max,
> + int (*unknown)(char *param, char *val,
> + const char *doing))
> +{
> + return NULL;
> +}
> +#endif
So this effectively disables parse_args() for all architectures, doesn't
it? If that's OK, I'd say the patch is x86 specific. Than it should
have, say, "x86:" as a prefix and it should be sent to the people and
lists taking care of x86.
But a quick grep suggests it's not OK to disable this for all other
architectures. Did I miss something with that quick grep?
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-05-19 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 11:50 [PATCH 1/3] kernel: Add a new config option to remove command line parsing Iulia Manda
2015-05-18 11:50 ` [PATCH 2/3] linux: Add macros that define and declare a core_param variable Iulia Manda
2015-05-18 11:50 ` [PATCH 3/3] init: Set initcall_debug to a default value Iulia Manda
2015-05-19 9:46 ` Paul Bolle
2015-05-20 0:54 ` josh
2015-05-19 9:35 ` Paul Bolle [this message]
2015-05-20 0:54 ` [PATCH 1/3] kernel: Add a new config option to remove command line parsing josh
2015-05-20 6:29 ` Rob Landley
2015-05-20 15:15 ` [PATCH v2] " Iulia Manda
[not found] <1427898893-8257-1-git-send-email-iulia.manda21@gmail.com>
2015-04-09 14:44 ` [PATCH 1/3] " Tim Bird
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=1432028159.9091.63.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=iulia.manda21@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@sonymobile.com \
/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