From: Rusty Russell <rusty@rustcorp.com.au>
To: "Jeremy Jackson" <jerj@coplanar.net>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Cc: "Bartlomiej Zolnierkiewicz" <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: [PATCH] Switch ide parameters to new-style and make them unique.
Date: Mon, 12 May 2003 16:37:29 +1000 [thread overview]
Message-ID: <20030512063812.EEDAF2C0F5@lists.samba.org> (raw)
In-Reply-To: Your message of "Sun, 11 May 2003 21:49:53 -0400." <003f01c31828$c8e9f480$7c07a8c0@kennet.coplanar.net>
In message <003f01c31828$c8e9f480$7c07a8c0@kennet.coplanar.net> you write:
> Cool stuff.
>
> As far as making the parameters easy to parse, I think you would want to
> have a single static tag before the = (equal) sign. The kernel command line
> parsing stuff provides parsing up to that point and dispatches to each
> subsystem (or at least it used to), so:
>
> ata.dev_noprobe=hda
>
> should be
>
> ata=dev_noprobe:hda,if_io_irq:0,0x1f0,7
>
> or some such to use the generic code that's already there.
Sure, some more complex generic parsing thing certainly makes sense.
I think whoever produces the code will probably get to decide what it
looks like.
Cheers!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-05-12 6:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 16:19 [PATCH] Parse new-style boot parameters just before initcalls Bartlomiej Zolnierkiewicz
2003-05-10 16:25 ` [PATCH] Switch ide parameters to new-style and make them unique Bartlomiej Zolnierkiewicz
2003-05-11 14:59 ` Jeremy Jackson
2003-05-11 15:32 ` Bartlomiej Zolnierkiewicz
2003-05-11 16:35 ` Alan Cox
2003-05-12 1:49 ` Jeremy Jackson
2003-05-12 6:37 ` Rusty Russell [this message]
2003-05-12 12:34 ` Bartlomiej Zolnierkiewicz
2003-05-12 2:21 ` Rusty Russell
2003-05-12 2:05 ` [PATCH] Parse new-style boot parameters just before initcalls Rusty Russell
2003-05-12 12:05 ` Bartlomiej Zolnierkiewicz
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=20030512063812.EEDAF2C0F5@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jerj@coplanar.net \
--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.