All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vamsi Krishna S ." <vamsi@in.ibm.com>
To: Rusty Russell <rusty@rustcorp.com.au>
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: Tue, 17 Dec 2002 11:48:46 +0530	[thread overview]
Message-ID: <20021217114846.A30837@in.ibm.com> (raw)
In-Reply-To: <20021217002740.598D32C05B@lists.samba.org>; from rusty@rustcorp.com.au on Tue, Dec 17, 2002 at 11:17:05AM +1100

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?

Thanks,
Vamsi.
-- 
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5044959
Internet: vamsi@in.ibm.com

  reply	other threads:[~2002-12-17  5:55 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 . [this message]
2002-12-18  0:23         ` Rusty Russell
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=20021217114846.A30837@in.ibm.com \
    --to=vamsi@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --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.