public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: mod filenames != modnames? (inconsistent name changing)
Date: Tue, 11 Jun 2013 17:14:15 -0700	[thread overview]
Message-ID: <51B7BD57.7050406@tlinx.org> (raw)

Should we have any expectation that a module name and it's filename
should be equivalent?

I was writing an auto-complete script for modprobe so it wouldn't give
me the option to double load a module (I'd have to manually type it in if
I really wanted it).

Trouble is some modules with names w/underscores ('_') change
register their names with a 'dash'.

Would it be too much trouble to ask that the same names be used in
both places?

I have about 30 modules loaded now and out of that list,
2 are name changes:

acpi_cpufreq  (filename acip-cpufreq.ko)
kvm_intel     (filename kvm-intel.ko)

If I load a bunch more... I find more that change names.

Could the naming in the modules that do this be made consistent?

Not doing so makes automatically tying a mod-name to it's file
tend toward being non-deterministic.

Many modules use '-' or '_' without being confused.
It would be helpful if the few confused modules could
get their identity straight.  Is there a problem with
making these names consistent?




             reply	other threads:[~2013-06-12  0:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12  0:14 Linda Walsh [this message]
2013-06-16  5:35 ` mod filenames != modnames? (inconsistent name changing) 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=51B7BD57.7050406@tlinx.org \
    --to=lkml@tlinx.org \
    --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