From: Rusty Russell <rusty@rustcorp.com.au>
To: Dave Jones <davej@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: obsolete modparam change busted.
Date: Tue, 09 Aug 2005 14:01:16 +1000 [thread overview]
Message-ID: <1123560076.13481.37.camel@localhost.localdomain> (raw)
In-Reply-To: <20050808184955.GA18779@redhat.com>
On Mon, 2005-08-08 at 14:49 -0400, Dave Jones wrote:
> However this change was broken, and if the modprobe.conf
> has trailing whitespace, modules fail to load with the
> following helpful message..
Hi Dave,
This fix should be preferable, I think.
Name: Ignore trailing whitespace on kernel parameters correctly
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Dave Jones says:
... if the modprobe.conf has trailing whitespace, modules fail to load
with the following helpful message..
snd_intel8x0: Unknown parameter `'
--- linux-2.6.12/kernel/params.c 2005-07-15 04:39:53.000000000 +1000
+++ /tmp/foo.c 2005-08-09 13:56:04.000000000 +1000
@@ -1,0 +1,0 @@
@@ -135,11 +80,8 @@
DEBUGP("Parsing ARGS: %s\n", args);
- while (*args) {
- int ret;
-
- args = next_arg(args, ¶m, &val);
- ret = parse_one(param, val, params, num, unknown);
+ while (*(args = next_arg(args, ¶m, &val))) {
+ int ret = parse_one(param, val, params, num, unknown);
switch (ret) {
case -ENOENT:
printk(KERN_ERR "%s: Unknown parameter `%s'\n",
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-08-09 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 18:49 obsolete modparam change busted Dave Jones
2005-08-09 4:01 ` Rusty Russell [this message]
2005-08-13 18:27 ` Dave Jones
2005-08-16 4:39 ` Rusty Russell
2005-08-16 5:16 ` Dave Jones
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=1123560076.13481.37.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--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