From: Petr Vorel <pvorel@suse.cz>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] dup07.c: Rewrite using new LTP API
Date: Mon, 11 Jul 2022 08:54:59 +0200 [thread overview]
Message-ID: <YsvJQ/plHHomtnvl@pevik> (raw)
In-Reply-To: <62C6452F.907@fujitsu.com>
Hi Avinesh, Xu,
> Hi Avinesh
> I did't look this cleanup patch, but I see the old code is same as
> dup202.c(This case covers more situation, ie using chmod). Maybe we can
> just add a test_variant to use dup syscall in dup202.c?
> Then remove this case directly.
+1, yes, the code in both tests indeed does the same.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-07-11 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 15:58 [LTP] [PATCH] dup07.c: Rewrite using new LTP API Avinesh Kumar
2022-07-07 1:29 ` xuyang2018.jy
2022-07-11 6:54 ` 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=YsvJQ/plHHomtnvl@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 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.