Re: [Xen-devel] [PATCH 1/3] cmdline_parse: Also pass bool_assert to OPT_CUSTOM so that parse_bool can be used correctly.

[Don Slutz <dslutz@xxxxxxxxxxx>]

On 07/29/14 02:35, Jan Beulich wrote:
> > > > On 28.07.14 at 22:30, <dslutz@xxxxxxxxxxx> wrote:
> > On 07/28/14 15:19, Keir Fraser wrote:
> > > Don Slutz wrote:

> I'd say we should allow what is sensible, and reject nonsense. E.g.
> "no-" on any option that has a value (following a = separator) makes
> no sense. But custom options allowing other than boolean values
> as their value can, when no value (and no = separator) was given,
> meaningfully be prefixed by "no-", which could be resolved by the
> faked up "=no" value I was suggesting in my earlier reply (at once
> dealing with "no-" prefixes on custom options not allowing boolean
> values: their parsing routine will simply reject the faked up "no").
v2 posted with this suggestion.

   -Don Slutz

> Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel