mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Crutcher Dunnavant <crutcher@datastacks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Whats in the wings for 2.5 (when it opens)
Date: Sat, 22 Sep 2001 12:59:20 +1000	[thread overview]
Message-ID: <17588.1001127560@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 21 Sep 2001 15:58:06 -0400." <20010921155806.B8188@mueller.datastacks.com>

On Fri, 21 Sep 2001 15:58:06 -0400, 
Crutcher Dunnavant <crutcher@datastacks.com> wrote:
>A cleaner handling of module parameters/cmd line options.

That comes out as a side effect of kernel build 2.5, every object gets
-DKBUILD_OBJECT to define the name it is known by.  From
Documentation/kbuild/kbuild-2.5.

      -DKBUILD_OBJECT=module, the name of the module the object is
        linked into, without the trailing '.o' and without any paths.
        If the object is a free standing module or is linked into
        vmlinux then the "module" name is the object itself.
        Automatically generated.

Post kbuild 2.5 I will be writing a generic parameter/command line
interface so you can insmod foo bar=99 or boot with foo.bar=99.  You
will even be able to boot with foo.bar=99 when foo is a module, insmod
will use the command line as a default set of values.


  reply	other threads:[~2001-09-22  3:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18  0:18 Ed Tomlinson
2001-09-18  1:24 ` David Weinehall
2001-09-18  2:24 ` James Simmons
2001-09-18 10:49 ` Gábor Lénárt
2001-09-18 19:49 ` toon
2001-09-21 19:58   ` Crutcher Dunnavant
2001-09-22  2:59     ` Keith Owens [this message]
2001-09-22 14:31       ` Crutcher Dunnavant
2001-09-22 14:44         ` Keith Owens
2001-09-22 15:23           ` Crutcher Dunnavant
2001-09-22 14:38     ` Arnaldo Carvalho de Melo
2001-09-23 13:42 ` José Luis Domingo López
2001-09-18 17:23 Grover, Andrew

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=17588.1001127560@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=crutcher@datastacks.com \
    --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

all inboxes | Powered by JetHome®