All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Schmidt <mschmidt@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] params: make dashes and underscores in parameter names truly equal
Date: Thu, 13 Oct 2011 16:41:11 +0200	[thread overview]
Message-ID: <4E96F887.5050103@redhat.com> (raw)
In-Reply-To: <8739exg588.fsf@rustcorp.com.au>

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()?
No objection to the change in do_early_param() ?

> 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

'log-buf-len=1M' does not work because it's an early_param(). 
'print_fatal_signals=1' does not work because it's defined as
__setup("print-fatal-signals=", ...);

> Perhaps we should work on converting
> them all, which would have beneficial side-effects as we poke into old
> code...

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.

Thanks,
Michal

  reply	other threads:[~2011-10-13 14:41 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 [this message]
2011-10-18  3:58     ` Rusty Russell
2011-10-18 19:01       ` Randy Dunlap
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=4E96F887.5050103@redhat.com \
    --to=mschmidt@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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.