public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
	linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: kernel param and KBUILD_MODNAME name-munging mess
Date: Wed, 22 Jan 2003 20:41:47 +0100	[thread overview]
Message-ID: <3E2EF3FB.4335D3F5@linux-m68k.org> (raw)
In-Reply-To: Pine.LNX.4.44.0301221112580.9969-100000@chaos.physics.uiowa.edu

Hi,

Kai Germaschewski wrote:

> KBUILD_BASENAME needs to be an un-stringified symbol following
> certain conventions to make it possible to use it e.g. in
> include/linux/spinlock.h, that's why '-' and ',' are escaped to '_'.
> 
> However, for all I can tell, this is not true for KBUILD_MODNAME, since
> that seems to be only used for constructing an actual string, which of
> course can contain all kinds of characters. So I think using the first
> approach would be somewhat nicer, as it gets rid of the unintuitive
> "ide-cd" -> "ide_cd" munging on the kernel command line.

It might be useful later to build a list of builtin modules. Currently
we do nothing if a builtin module fails to initialize, but we should
disable dependent modules and remove the exported symbols.
Maybe it's better to provide the module name both as label and string.

bye, Roman


  reply	other threads:[~2003-01-22 19:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 13:41 kernel param and KBUILD_MODNAME name-munging mess Mikael Pettersson
2003-01-21  6:26 ` Vamsi Krishna S.
2003-01-21  7:23 ` Rusty Russell
2003-01-22  9:51 ` Ingo Oeser
2003-01-22 10:20   ` Mikael Pettersson
2003-01-22 11:19     ` Alex Riesen
2003-01-22 17:25     ` Kai Germaschewski
2003-01-22 19:41       ` Roman Zippel [this message]
2003-01-28  9:15     ` 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=3E2EF3FB.4335D3F5@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox