public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib: Add library function for parsing kernel config
Date: Fri, 16 Nov 2018 14:57:47 +0100	[thread overview]
Message-ID: <20181116135747.GE29013@rei.lan> (raw)
In-Reply-To: <ECADFF3FD767C149AD96A924E7EA6EAF88A40FCE@USCULXMSG01.am.sony.com>

Hi!
> This is good.  Just a comment on the proposed syntax and options.
> Fuego uses NEED_KCONFIG (upper-case because it's a shell global variable),
> and 0-day uses need_kconfig.
> 
> There are a few slight differences in syntax between different systems.
> (I'm making no judgements, just noting the differences).
> 
> Fuego and 0day also support a string including the option value, such
> as:
>  CONFIG_PRINTK=y
>  CONFIG_LOCKDEP_SUPPORT=n
>  CONFIG_CAN=m

I guess that it makes sense to support this as well.

I can easily switch to verbatim match if the option I'm looking for
contains '='.

> See https://elinux.org/Test_Dependencies
> 
> where I've started collecting some of these different syntaxes.

Thanks for the pointer, I will look into that.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2018-11-16 13:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 13:44 [LTP] [PATCH] lib: Add library function for parsing kernel config Cyril Hrubis
2018-11-15 18:57 ` Cristian Marussi
2018-11-16 13:53   ` Cyril Hrubis
2018-11-15 20:16 ` Tim.Bird
2018-11-16 13:59   ` Cyril Hrubis
2018-11-21 19:53     ` Tim.Bird
2018-11-15 20:43 ` Tim.Bird
2018-11-16 13:57   ` Cyril Hrubis [this message]
2018-11-16  3:54 ` Pengfei Xu
2018-11-16  4:03   ` Tim.Bird
2018-11-16  4:57     ` Pengfei Xu
2018-11-16 14:00   ` Cyril Hrubis
2018-11-17  5:41     ` Pengfei Xu
2018-11-23  4:56 ` Sandeep Patil

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=20181116135747.GE29013@rei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox