From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] network/nsf_lib.sh: TCONF on mount (udp/udp6) failure for Linux v5.6+
Date: Thu, 18 Jun 2020 15:49:45 +0200 [thread overview]
Message-ID: <20200618134945.GA21692@dell5510> (raw)
In-Reply-To: <8b5eef18-1c3e-d89c-9af2-b27828f3cb02@oracle.com>
Hi Li, Alexey, Cyril,
> > Requiring kernel config is ok for traditional distros (and even here is
> > sometimes readable only for root, e.g. Debian/Ubuntu), but it's still rare on
> > arm (other embedded archs). I guess it'd be nice to have some variable, which
> > would turn kernel config based requirement into warning.
> Also the option's name can be renamed in new releases, so the decision
> should be made only if the option is found (i.e. if we check without the
> the kernel version).
FYI (you may have noticed) there was an effort to add boolean OR for C
implementation:
https://patchwork.ozlabs.org/project/ltp/list/?series=149804&state=*
> tst_check_kconfig - will be really nice to have.
+1. Is anybody planning to work on it?
> Then, we will tconf
> earlier in the setup if this option is found.
> What about TCONF_IF_KCONFIG, in addition to NEEDS_KCONFIG?
+1 (+ add it to C as well).
Kind regards,
Petr
next prev parent reply other threads:[~2020-06-18 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 15:49 [LTP] [PATCH] network/nsf_lib.sh: TCONF on mount (udp/udp6) failure for Linux v5.6+ Alexey Kodanev
2020-06-18 3:15 ` Li Wang
2020-06-18 5:51 ` Petr Vorel
2020-06-18 9:36 ` Petr Vorel
2020-06-18 13:24 ` Alexey Kodanev
2020-06-18 13:49 ` Petr Vorel [this message]
2020-06-19 2:56 ` Li Wang
2020-06-22 13:34 ` Petr Vorel
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=20200618134945.GA21692@dell5510 \
--to=pvorel@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