public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Avinesh Kumar <akumar@suse.de>
To: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] doc/C-API: Move .min_mem_avail below .min_cpus
Date: Thu, 29 Jun 2023 09:54:08 +0530	[thread overview]
Message-ID: <2692871.mvXUDI8C0e@localhost> (raw)
In-Reply-To: <20230627183114.89536-1-pvorel@suse.cz>

Reviewed-by: Avinesh Kumar <akumar@suse.de>

On Wednesday, June 28, 2023 12:01:14 AM IST Petr Vorel wrote:
> From: Petr Vorel <petr.vorel@gmail.com>
> 
> Required minimum of CPU and RAM are related topics,
> it's better to have together.
> 
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
>  doc/c-test-api.txt | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/doc/c-test-api.txt b/doc/c-test-api.txt
> index dcb6e1ba8..9106758d7 100644
> --- a/doc/c-test-api.txt
> +++ b/doc/c-test-api.txt
> @@ -2328,7 +2328,13 @@ both V1 and V2 feasible.
>  Some tests require more than specific number of CPU. It can be defined with
> `.min_cpus = N`.
> 
> -1.38 Test tags
> +1.38 Require minimum size of MemAvailable for a testcase
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +Some tests require more than specific size(MB) of MemAvailable. It can be
> defined +with `.min_mem_avail = N`.
> +
> +1.39 Test tags
>  ~~~~~~~~~~~~~~
> 
>  Test tags are name-value pairs that can hold any test metadata.
> @@ -2370,7 +2376,7 @@ struct tst_test test = {
>  };
>  ---------------------------------------------------------------------------
> ----
> 
> -1.39 Testing on the specific architecture
> +1.40 Testing on the specific architecture
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  Testcases for specific arch should be limited on that only being supported
>  platform to run, we now involve a .supported_archs to achieve this feature
> @@ -2406,12 +2412,6 @@ static struct tst_test test = {
>  };
>  ---------------------------------------------------------------------------
> ----
> 
> -1.40 Require minimum size of MemAvailable for a testcase
> -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> -
> -Some tests require more than specific size(MB) of MemAvailable. It can be
> defined -with `.min_mem_avail = N`.
> -
>  2. Common problems
>  ------------------





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

  reply	other threads:[~2023-06-29  4:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 18:31 [LTP] [PATCH 1/1] doc/C-API: Move .min_mem_avail below .min_cpus Petr Vorel
2023-06-29  4:24 ` Avinesh Kumar [this message]
2023-06-29 13:35   ` 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=2692871.mvXUDI8C0e@localhost \
    --to=akumar@suse.de \
    --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