From: Petr Vorel <pvorel@suse.cz>
To: "Yang Xu (Fujitsu)" <xuyang2018.jy@fujitsu.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 1/3] link03: Convert docs to docparse
Date: Fri, 3 Nov 2023 08:32:46 +0100 [thread overview]
Message-ID: <20231103073246.GB998015@pevik> (raw)
In-Reply-To: <TYWPR01MB11829EF94773BEC2AD0A8E95FFDA0A@TYWPR01MB11829.jpnprd01.prod.outlook.com>
Hi Xu,
> Hi Petr,
> I've noticed that the test objectives of link03 and link05 are very similar, and the description of link05's test has no relevance to the test code.
> Therefore, I think we can simply remove link03 and update the test description of link05 to replace link03.
> As for your previous suggestions for modifying the link05 code, I don't have a good solution for this.
> The specific information is as follows:
> LINK: http://patchwork.ozlabs.org/project/ltp/patch/1697021709-22916-2-git-send-email-xuyang2018.jy@fujitsu.com/
Indeed, test would have to print ouput 1000x, because each test needs to report
result. Therefore let's keep it. I hope it makes sense to run test 1000x.
E.g. feel free to merge (ideally with fixes spaces to tags, but understand if
you do just docparse change).
Kind regards,
Petr
> Best Regards,
> Yang Xu
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-11-03 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 10:55 [LTP] [PATCH 1/3] link03: Convert docs to docparse Yang Xu
2023-10-11 10:55 ` [LTP] [PATCH 2/3] link05: " Yang Xu
2023-10-12 10:08 ` Petr Vorel
2023-10-17 6:11 ` Yang Xu (Fujitsu)
2023-10-11 10:55 ` [LTP] [PATCH 3/3] link08: " Yang Xu
2023-10-12 9:58 ` Petr Vorel
2023-10-13 5:49 ` Yang Xu (Fujitsu)
2023-10-12 10:00 ` Petr Vorel
2023-10-13 5:45 ` Yang Xu (Fujitsu)
2023-10-12 9:55 ` [LTP] [PATCH 1/3] link03: " Petr Vorel
2023-10-13 5:43 ` Yang Xu (Fujitsu)
2023-10-13 6:12 ` Petr Vorel
2023-10-25 23:51 ` Petr Vorel
2023-10-26 7:37 ` [LTP] 回复: " Yang Xu (Fujitsu)
2023-10-31 7:22 ` [LTP] " Yang Xu (Fujitsu)
2023-11-03 7:32 ` Petr Vorel [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=20231103073246.GB998015@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox