From: Rusty Russell <rusty@rustcorp.com.au>
To: Corey Minyard <minyard@acm.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] IPMI driver updates, part 3
Date: Fri, 27 Feb 2004 09:48:33 +1100 [thread overview]
Message-ID: <20040226225419.20A032C360@lists.samba.org> (raw)
In-Reply-To: Your message of "Mon, 23 Feb 2004 10:02:50 MDT." <403A242A.6000802@acm.org>
In message <403A242A.6000802@acm.org> you write:
> + insmod ipmi_smb_intf.o
> + smb_addr=<adapter1>,<i2caddr1>[,<adapter2>,<i2caddr2>[,...]]
> + smb_dbg=<flags1>,<flags2>...
> + [smb_defaultprobe=0] [smb_dbg_probe=1]
Please use "modprobe" not "insmod" in examples, and drop the ".o"
extension.
> +When compiled into the kernel, the addresses can be specified on the
> +kernel command line as:
> +
> + ipmi_smb=[<adapter1>.]<addr1>[:<debug1>],[<adapter2>.<addr2>[:<debug1>]....
I realize this is traditional. However, I suggest you:
1) Rename the module to impi_smb.
2) Change the variable names to addr, debug, debug_probe and
default_probe.
3) Change MODULE_PARM to module_param
4) Get rid of the #ifndef MODULE code.
The results will be symmetry, and less code:
modprobe ipmi_smb addr=<adapter1>,<i2caddr1>[,<adapter2>,<i2caddr2>[,...]]
debug=<flags1>,<flags2>...
default_probe=0 debug_probe=1
and
boot ipmi_smb.addr=... ipmi_smb.debug=... ipmi.default_probe=0 ipmi.debug_probe=1
Of course, if you really want to you can use module_param_named and
keep the variable names the same as they are now, and "#undef
KBUILD_MODNAME // #define KBUILD_MODNAME ipmi_smb", to avoid renaming
your module.
But I really think the module name wants a revisit (although I have no
idea what it does, so might be wrong).
Cheers!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2004-02-26 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 16:02 [PATCH] IPMI driver updates, part 3 Corey Minyard
2004-02-26 22:48 ` Rusty Russell [this message]
2004-02-27 13:49 ` Corey Minyard
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=20040226225419.20A032C360@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.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 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.