From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] Refactor fork10 test using new LTP API
Date: Tue, 28 Nov 2023 13:52:27 +0100 [thread overview]
Message-ID: <20231128125227.GA381183@pevik> (raw)
In-Reply-To: <ZUTNj43_CYMi0m38@yuki>
Hi Cyril, Andrea,
> Hi!
> Pushed with two minor changes, thanks.
> 1. Used the more usuall condition for open fd in cleanup
> 2. Change SAFE_READ() to pass 1 for len_strict so that we are sure whole
> block was read
I see the original test forked twice. I suppose for testing purposes only single
fork is enough.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-11-28 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 7:34 [LTP] [PATCH v1] Refactor fork10 test using new LTP API Andrea Cervesato
2023-11-03 10:38 ` Cyril Hrubis
2023-11-28 12:52 ` 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=20231128125227.GA381183@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox