From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] doc: Drop uClinux support
Date: Mon, 31 May 2021 05:37:37 +0200 [thread overview]
Message-ID: <YLRaAWP7A0RdleuX@pevik> (raw)
In-Reply-To: <20210531032910.6739-1-pvorel@suse.cz>
Hi,
[Cc: Mike ]
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Hi,
> some shorter form could be added to 3. Test Contribution Checklist [1] as well.
> Kind regards,
> Petr
> [1] https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#3-test-contribution-checklist
> doc/maintainer-patch-review-checklist.txt | 3 +++
> 1 file changed, 3 insertions(+)
> diff --git a/doc/maintainer-patch-review-checklist.txt b/doc/maintainer-patch-review-checklist.txt
> index 5420fa933..81ed61ddf 100644
> --- a/doc/maintainer-patch-review-checklist.txt
> +++ b/doc/maintainer-patch-review-checklist.txt
> @@ -44,6 +44,9 @@ New test should
> * Docparse documentation
> * If a test is a regression test it should include tags
> (more in https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#2238-test-tags[Test tags])
> +* When rewritting old tests, https://en.wikipedia.org/wiki/%CE%9CClinux[uClinux
> + (?Clinux)] support should be removed (project has been discontinued).
> + E.g. `FORK_OR_VFORK()` should be replaced with simple `fork()` or `SAFE_FORK()`.
> ### Shell tests
> * Use new https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines#23-writing-a-testcase-in-shell[shell API]
FYI: https://github.com/uclinux-dev
But that's just archiving the project, it's safe to remove uclinux support from
LTP.
Kind regards,
Petr
next prev parent reply other threads:[~2021-05-31 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 3:29 [LTP] [PATCH 1/1] doc: Drop uClinux support Petr Vorel
2021-05-31 3:37 ` Petr Vorel [this message]
2021-05-31 8:56 ` Cyril Hrubis
2021-05-31 14:54 ` Petr Vorel
2021-06-02 11:18 ` 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=YLRaAWP7A0RdleuX@pevik \
--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 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.