All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH] API: Allow testing of kernel features in development
Date: Wed, 5 Jan 2022 17:00:06 +0100	[thread overview]
Message-ID: <YdXAhgvstNcDz7WY@yuki> (raw)
In-Reply-To: <YdW/0BUm+vBY3PHy@yuki>

Hi!
> I would be even tempted to add this to the default syscalls runtest file
> but render the test resultless, e.g. replace the tst_res() and tst_brk()
> handlers in tst_res.c so that it will print only INFO messages.

And that would also allow us to have env variable switch that would
enable all tests for unrelased features, something as
LTP_ENABLE_UNRELASED or so. Also with that we can really just TCONF if
that variable is not set which would be much simpler.

-- 
Cyril Hrubis
chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-01-05 15:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211220180748.36A90A3B8E@relay2.suse.de>
2021-12-21 11:30 ` [LTP] [RFC PATCH] API: Allow testing of kernel features in development Richard Palethorpe via ltp
2021-12-21 12:14   ` Li Wang
2021-12-21 13:56     ` Richard Palethorpe
2021-12-21 17:56   ` Petr Vorel
2021-12-22  8:41     ` Jan Stancek
2021-12-22  8:44       ` Richard Palethorpe
2021-12-22  9:29       ` Petr Vorel
2022-01-05 15:57   ` Cyril Hrubis
2022-01-05 16:00     ` Cyril Hrubis [this message]
2022-01-10  8:09       ` Richard Palethorpe
2022-01-28 12:32         ` Petr Vorel
2022-02-03 10:18           ` [LTP] [PATCH] Create policy for testing unstable kernel features Richard Palethorpe via ltp
2022-02-03 10:22             ` Petr Vorel
2022-02-04  7:46             ` Jan Stancek
2022-02-08  8:18             ` Li Wang
2022-03-03 13:33               ` Petr Vorel
2022-06-14 12:31                 ` Petr Vorel
2022-06-14 13:13                   ` Cyril Hrubis
2022-06-16  8:25                     ` 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=YdXAhgvstNcDz7WY@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.com \
    /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.