public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Pavel Roskin <proski@gnu.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fw: [PATCH] Re: module_param() doesn't seem to work in 2.6.6-rc1
Date: Sun, 18 Apr 2004 09:21:00 +1000	[thread overview]
Message-ID: <1082244060.14091.2.camel@bach> (raw)
In-Reply-To: <20040417011836.318c679b.akpm@osdl.org>

On Sat, 2004-04-17 at 18:18, Andrew Morton wrote:
> OK?

Yes, but I prefer this version, which actually checks whether the
section exists, rather than checking the size (same effect, but this is
clearer).

Name: Warn if module_param and MODULE_PARM mixed
Status: Trivial
From: Pavel Roskin <proski@gnu.org>

If you use both module_param (new) and MODULE_PARM (obsolete) in a
module, only the second gets recognised.  Warn.

diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal .14500-linux-2.6.6-rc1-bk1/kernel/module.c .14500-linux-2.6.6-rc1-bk1.updated/kernel/module.c
--- .14500-linux-2.6.6-rc1-bk1/kernel/module.c	2004-04-15 16:06:55.000000000 +1000
+++ .14500-linux-2.6.6-rc1-bk1.updated/kernel/module.c	2004-04-18 09:17:26.000000000 +1000
@@ -1541,6 +1541,10 @@ static struct module *load_module(void _
 				      / sizeof(struct obsolete_modparm),
 				      sechdrs, symindex,
 				      (char *)sechdrs[strindex].sh_addr);
+		if (setupindex)
+			printk(KERN_WARNING "%s: Ignoring new-style "
+			       "parameters in presence of obsolete ones\n",
+			       mod->name);
 	} else {
 		/* Size of section 0 is 0, so this works well if no params */
 		err = parse_args(mod->name, mod->args,

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


           reply	other threads:[~2004-04-17 23:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20040417011836.318c679b.akpm@osdl.org>]

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=1082244060.14091.2.camel@bach \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.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