All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: vamsi@in.ibm.com
Cc: Zwane Mwaikambo <zwane@holomorphy.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] module-init-tools 0.9.3, rmmod modules with '-'
Date: Wed, 18 Dec 2002 11:23:35 +1100	[thread overview]
Message-ID: <20021218022816.913AC2C238@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 17 Dec 2002 11:48:46 +0530." <20021217114846.A30837@in.ibm.com>

In message <20021217114846.A30837@in.ibm.com> you write:
> On Tue, Dec 17, 2002 at 11:17:05AM +1100, Rusty Russell wrote:
> > 
> > BTW, this was done for (1) simplicity, (2) so KBUILD_MODNAME can be
> > used to construct identifiers, and (3) so parameters when the module
> > is built-in have a consistent name.
> > 
> Ok, I see it now, this magic happens in scripts/Makefile.lib. 
> My module has been built outside the kernel build system, that's
> why I saw this problem.
> 
> I guess avoiding '-' should do it, but is there a simple way to 
> correctly build (simple, test) modules outside the kernel tree now?

Has there ever been a simple way?  You can either use _ in the name,
or use tr on the -DKBUILD_MODNAME line, I guess.

Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2002-12-18  2:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 11:06 [BUG] module-init-tools 0.9.3, rmmod modules with '-' Vamsi Krishna S .
2002-12-16 21:36 ` Rusty Russell
2002-12-16 23:39   ` Zwane Mwaikambo
2002-12-17  0:17     ` Rusty Russell
2002-12-17  6:18       ` Vamsi Krishna S .
2002-12-18  0:23         ` Rusty Russell [this message]
2002-12-18 17:47           ` Kai Germaschewski
2002-12-19  0:39             ` Rusty Russell
2002-12-19  7:11             ` Vamsi Krishna S .
  -- strict thread matches above, loose matches on Subject: below --
2002-12-17  6:55 Osamu Tomita

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=20021218022816.913AC2C238@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vamsi@in.ibm.com \
    --cc=zwane@holomorphy.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 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.