From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/3] lib/tst_kconfig: Rewrite the parser internals
Date: Thu, 22 Oct 2020 10:53:50 +0200 [thread overview]
Message-ID: <20201022085350.GA2427@yuki.lan> (raw)
In-Reply-To: <87mu0evfzv.fsf@suse.de>
Hi!
> > I do not get what you are trying to say. Are you saying that we should
> > tokenize the input? I do not think that this is necessary since the file
> > format is pretty simple.
>
> Yes or atleast test the assumption you won't find configs with spaces or
> other wierd stuff in by throwing an error if we find something
> unexpected. If someone has a broken config we can tell them that.
I guess I can make it a bit more robust in a follow up patch.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-10-22 8:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 10:09 [LTP] [PATCH 0/3] Add support for kconfig constraints Cyril Hrubis
2020-10-20 10:09 ` [LTP] [PATCH 1/3] lib/tst_kconfig: Rewrite the parser internals Cyril Hrubis
2020-10-21 9:46 ` Richard Palethorpe
2020-10-21 10:06 ` Cyril Hrubis
2020-10-21 12:39 ` Richard Palethorpe
2020-10-21 14:11 ` Cyril Hrubis
2020-10-21 14:31 ` [LTP] [Automated-testing] " Petr Vorel
2020-10-22 8:09 ` [LTP] " Richard Palethorpe
2020-10-22 8:53 ` Cyril Hrubis [this message]
2020-10-20 10:09 ` [LTP] [PATCH 2/3] lib: Add generic boolean expression parser and eval Cyril Hrubis
2020-10-21 16:34 ` Richard Palethorpe
2020-10-21 16:36 ` Richard Palethorpe
2020-10-21 18:20 ` Cyril Hrubis
2020-10-22 7:55 ` Richard Palethorpe
2020-10-22 8:57 ` Cyril Hrubis
2020-10-22 10:28 ` Richard Palethorpe
2020-10-20 10:09 ` [LTP] [PATCH 3/3] lib/tst_kconfig: Make use of boolean expression eval Cyril Hrubis
2020-10-22 8:38 ` Richard Palethorpe
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=20201022085350.GA2427@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.