From: Randy Dunlap <rdunlap@xenotime.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Michal Schmidt <mschmidt@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] params: make dashes and underscores in parameter names truly equal
Date: Tue, 18 Oct 2011 12:01:00 -0700 [thread overview]
Message-ID: <4E9DCCEC.4090105@xenotime.net> (raw)
In-Reply-To: <87obxfq7bd.fsf@rustcorp.com.au>
On 10/17/2011 08:58 PM, Rusty Russell wrote:
> On Thu, 13 Oct 2011 16:41:11 +0200, Michal Schmidt <mschmidt@redhat.com> wrote:
>> On 10/13/2011 01:28 AM, Rusty Russell wrote:
>>> Idea is solid, implementation has a few quirks. As the name
>>> obsolete_checksetup() implies, this was only supposed to be a crutch for
>>> old __setup() calls. Modern code should be using module_param() or
>>> core_param().
>>
>> ... instead of __setup()?
>
> Yep.
>
>> No objection to the change in do_early_param() ?
>
> Well, for the moment I've applied that, with parameq and parameqn
> reimplemented more cleanly. See below.
>
>>> Did you have a specific example?
>>
>> The specific example I had in mind was the one from
>> Documentation/kernel-parameters.txt:
>>
>> log_buf_len=1M print-fatal-signals=1
>> can also be entered as
>> log-buf-len=1M print_fatal_signals=1
>
> Oops.
>
>> Let's see how many __setup() parameters there are:
>> $ git grep -E '^__setup\("' |wc -l
>> 457
>>
>> Only the ones with a dash or underscore in the name:
>> $ git grep -E '__setup\(".*[_-].*"' | wc -l
>> 180
>>
>> It will take some time.
>
> The easy things have already been done ;)
>
> Just do the non-arch ones, first, and see where that gets us.
>
> Thanks!
> Rusty.
>
> From: Michal Schmidt <mschmidt@redhat.com>
> Subject: params: make dashes and underscores in parameter names truly equal
> Date: Mon, 10 Oct 2011 00:03:37 +0200
>
> The user may use "foo-bar" for a kernel parameter defined as "foo_bar".
> Make sure it works the other way around too.
>
> Apply the equality of dashes and underscores on early_params and __setup
> params as well.
>
> The example given in Documentation/kernel-parameters.txt indicates that
> this is the intended behaviour.
Well, that could have just been my misunderstanding, but I think that this
patch is the right thing to do. Thanks.
> With the patch the kernel accepts "log-buf-len=1M" as expected.
> https://bugzilla.redhat.com/show_bug.cgi?id=744545
>
> Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (neatened implementations)
> ---
> include/linux/moduleparam.h | 20 ++++++++++++++++++++
> init/main.c | 4 ++--
> kernel/params.c | 21 ++++++++++++++-------
> 3 files changed, 36 insertions(+), 9 deletions(-)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-10-18 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 22:03 [PATCH] params: make dashes and underscores in parameter names truly equal Michal Schmidt
2011-10-12 23:28 ` Rusty Russell
2011-10-13 14:41 ` Michal Schmidt
2011-10-18 3:58 ` Rusty Russell
2011-10-18 19:01 ` Randy Dunlap [this message]
2011-10-19 3:00 ` Rusty Russell
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=4E9DCCEC.4090105@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.