public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] doc: Add basic shell test description
Date: Tue, 25 Nov 2025 10:49:34 +0100	[thread overview]
Message-ID: <aSV7rkCd_RjpYkbx@yuki.lan> (raw)
In-Reply-To: <20251124175951.GA127343@pevik>

Hi!
> > +    'shell_lib': (f'{ltp_repo}/blob/master/testcases/lib/%s', '%s'),
> +1. I was thinking about it previously for C helpers, then I preferred to show
> full path. I guess I'll later use 'shell_lib' prefix for these. I suppose we can
> keep lib/*.c path, but sure, we could also (later) add 'lib' and 'include'.

Well this is going to be easier to maintain if we ever decided to move
the content of the testcases/lib into a top level directory, where it
probably belongs.

> I wish extlinks module allow to pass more params than just one.

Yes.

> +++ doc/developers/api_shell_tests.rst
> @@ -87,9 +87,9 @@ Test setup and cleanup
>  ----------------------
>  
>  The test setup and cleanup functions are optional and passed via variables.
> -Similarily to the C API the setup is executed exactly once at the start of the
> +Similarly to the C API the setup is executed exactly once at the start of the
>  test and the test cleanup is executed at the test end or when test was
> -interrupted by ref:`tst_brk`.
> +interrupted by :ref:`tst_brk`.
>  
>     .. literalinclude:: ../../testcases/lib/tests/shell_loader_setup_cleanup.sh
> -   :language: shell
> +      :language: shell

Fixed and pushed, thanks.

-- 
Cyril Hrubis
chrubis@suse.cz

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

      reply	other threads:[~2025-11-25  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 16:43 [LTP] [PATCH v2] doc: Add basic shell test description Cyril Hrubis
2025-11-24 17:59 ` Petr Vorel
2025-11-25  9:49   ` Cyril Hrubis [this message]

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=aSV7rkCd_RjpYkbx@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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