All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: usb-snd-audio breakage
Date: Mon, 26 Sep 2005 09:32:43 -0400	[thread overview]
Message-ID: <9e473391050926063264010349@mail.gmail.com> (raw)
In-Reply-To: <20050926033805.GB22376@redhat.com>

So module and proc code will strip white space, but sysfs won't strip
white space. Where is the consistency?

On 9/25/05, Dave Jones <davej@redhat.com> wrote:
> On Sun, Sep 25, 2005 at 10:43:11PM -0400, Jon Smirl wrote:
>  > The Redhat FC4 installer is adds index=0 in modprobe.conf. The index
>  > parameter appears to have been removed fron snd-usb-audio.
>  >
>  > There are two issues:
>  > 1) should index have been left as a non-functioning param so that
>  > existing installs won't break.
>  > 2) Why didn't I get a decent error message about index being the
>  > problem instead of the message about `'
>
> This patch really should have been merged for 2.6.13
> but somehow fell through the cracks. I don't think it
> even landed in -mm
>
>                 Dave
>
>
>
> Name: Ignore trailing whitespace on kernel parameters correctly: Fixed version
> 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 `'
>
> Previous version truncated last argument.
>
> Index: linux-2.6.13-rc6-git7-Module/kernel/params.c
> ===================================================================
> --- linux-2.6.13-rc6-git7-Module.orig/kernel/params.c   2005-08-10 16:12:45.000000000 +1000
> +++ linux-2.6.13-rc6-git7-Module/kernel/params.c        2005-08-16 14:31:16.000000000 +1000
> @@ -80,8 +80,6 @@
>         int in_quote = 0, quoted = 0;
>         char *next;
>
> -       /* Chew any extra spaces */
> -       while (*args == ' ') args++;
>         if (*args == '"') {
>                 args++;
>                 in_quote = 1;
> @@ -121,6 +119,9 @@
>                 next = args + i + 1;
>         } else
>                 next = args + i;
> +
> +       /* Chew up trailing spaces. */
> +       while (*next == ' ') next++;
>         return next;
>  }
>
> @@ -134,6 +135,9 @@
>         char *param, *val;
>
>         DEBUGP("Parsing ARGS: %s\n", args);
> +
> +       /* Chew leading spaces */
> +       while (*args == ' ') args++;
>
>         while (*args) {
>                 int ret;
>
>
>


--
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2005-09-26 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26  2:27 usb-snd-audio breakage Jon Smirl
2005-09-26  2:43 ` Jon Smirl
2005-09-26  3:38   ` Dave Jones
2005-09-26 13:32     ` Jon Smirl [this message]
2005-09-26 15:07       ` Greg KH
2005-09-26 15:54         ` Jon Smirl
2005-09-26 20:13           ` Greg KH

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=9e473391050926063264010349@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=davej@redhat.com \
    --cc=greg@kroah.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 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.