From: Chris Wright <chrisw@osdl.org>
To: Chris Wright <chrisw@osdl.org>,
linux-kernel@vger.kernel.org, Nick.Holloway@pyrites.org.uk
Subject: Re: [PATCH 2.6] Add missing MODULE_PARAM to dummy.c (and MAINTAINERShip)
Date: Thu, 8 Apr 2004 12:29:30 -0700 [thread overview]
Message-ID: <20040408122930.S21045@build.pdx.osdl.net> (raw)
In-Reply-To: <20040408185903.GA21236@localhost>; from linux-kernel@24x7linux.com on Thu, Apr 08, 2004 at 08:59:03PM +0200
* Jose Luis Domingo Lopez (linux-kernel@24x7linux.com) wrote:
> On Thursday, 08 April 2004, at 10:54:40 -0700,
> Chris Wright wrote:
>
> > this is going backwards. module_param is the newer (preferred) interface.
> >
> I (incorrectly) based my assumptions on the fact that "modinfo dummy"
> didn't return any information about the module parameter. I also had a
> look at some other modules, like "bonding", "rtl8139", and I assumed
> that the MODULE_* macros were the 2.6.x way of doing things.
It's a mix. module_param(), MODULE_PARM_DESC(), MODULE_LICENSE(),
MODULE_AUTHOR(), MODULE_DESCRIPTION().
So the whole patch isn't bad, just the bit like:
-module_param()
+MODULE_PARM()
> I was obviously wrong, sorry for the waste of time (anyways, it seems
> there are several kernel modules waiting to be updated, maybe I should
> give them a look and learn something and try to "fix" them).
Sure, although some of these changes may not be accepted simply because
they create noise, patch conflicts etc at a time where stability is more
important. So new code should use the new ones, old code may not all be
converted for some time.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-04-08 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 17:48 Jose Luis Domingo Lopez
2004-04-08 17:54 ` Chris Wright
2004-04-08 18:59 ` Jose Luis Domingo Lopez
2004-04-08 19:29 ` Chris Wright [this message]
2004-04-08 19:10 ` Nick Holloway
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=20040408122930.S21045@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=Nick.Holloway@pyrites.org.uk \
--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
all inboxes | Powered by JetHome®