From: Daniel Mierswa <impulze@impulze.org>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Re: Parsing kernel parameters and escaping "
Date: Tue, 07 Jul 2009 01:03:16 +0200 [thread overview]
Message-ID: <4A5282B4.8070302@impulze.org> (raw)
In-Reply-To: <4A50B09B.9030901@impulze.org>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
As stated in my last E-Mail in this thread there are currently some
limitations when passing quotes to kernel parameters, I tried to remove
some of those limitations. A git fp is attached.
(from the commit message):
> There was a limitation for kernel parameters with regards to quoting. It
> wasn't possible to escape quotes or use quotes to form space-filled
> values _inside_ parameters. This patch attempts to make that possible,
> kernel parameters are now parsed as follows:
> '"param= value"' [param= value][]
> 'param=" value "" combination "' [param][ value combination ]
> 'param=" \" test"' [param][ " test]
> '"param"=another' [param][another]
Any suggestions welcome. Please be kind, as I'm not too familar with
writing parsers, kernel development and what I may have broke. :-)
--
Mierswa, Daniel
If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-07-06 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-05 13:54 Parsing kernel parameters and escaping " Daniel Mierswa
2009-07-06 23:03 ` Daniel Mierswa [this message]
2009-07-06 23:05 ` [RFC] " Daniel Mierswa
2009-07-07 0:54 ` Daniel Mierswa
2009-07-12 9:41 ` Rusty Russell
2009-07-12 17:59 ` Daniel Mierswa
2009-07-12 23:57 ` Rusty Russell
2009-07-13 2:49 ` Daniel Mierswa
2009-07-14 2:49 ` Rusty Russell
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=4A5282B4.8070302@impulze.org \
--to=impulze@impulze.org \
--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.