From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: QI Fuli <fukuri.sai@gmail.com>
Cc: "qi.fuli@fujitsu.com" <qi.fuli@fujitsu.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v3 5/5] syscalls/dup2: rename dup205 to dup204
Date: Fri, 17 Sep 2021 03:20:52 +0000 [thread overview]
Message-ID: <614409AA.6080809@fujitsu.com> (raw)
Message-ID: <20210917032052.LS7HBGM3jMeTh3-Ng7bJTSdcawgmuSpTUROsseoClhM@z> (raw)
In-Reply-To: <20210916104933.33409-6-qi.fuli@fujitsu.com>
Hi Qi
> From: QI Fuli<qi.fuli@fujitsu.com>
>
> Signed-off-by: QI Fuli<qi.fuli@fujitsu.com>
> ---
> testcases/kernel/syscalls/dup2/{dup205.c => dup204.c} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename testcases/kernel/syscalls/dup2/{dup205.c => dup204.c} (100%)
You miss .gitnore and runtest/syscalls. We also need to remove dup205
tag in them.
No need v4. Maintainer Will remove them when merging this patchset.
Other than some nits(useless comments, empty line, whitespace), this
patchset looks good to me.
Reviewed-by: Yang Xu <xuyang2018.jy@fujitsu.com>
Best Regards
Yang Xu
>
> diff --git a/testcases/kernel/syscalls/dup2/dup205.c b/testcases/kernel/syscalls/dup2/dup204.c
> similarity index 100%
> rename from testcases/kernel/syscalls/dup2/dup205.c
> rename to testcases/kernel/syscalls/dup2/dup204.c
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-09-17 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 10:49 [LTP] [PATCH v3 0/5] Convert syscalls/dup2/dup2{01...05} to new API QI Fuli
2021-09-16 10:49 ` QI Fuli
2021-09-16 10:49 ` [LTP] [PATCH v3 1/5] syscalls/dup2/dup201: Convert " QI Fuli
2021-09-16 10:49 ` QI Fuli
2021-09-17 7:04 ` Xiao Yang
2021-09-17 7:04 ` Xiao Yang
2021-09-16 10:49 ` [LTP] [PATCH v3 2/5] syscalls/dup2/dup202: Convert to new API and merge dup204 into dup202 QI Fuli
2021-09-16 10:49 ` QI Fuli
2021-09-17 7:27 ` Xiao Yang
2021-09-17 7:27 ` Xiao Yang
2021-09-16 10:49 ` [LTP] [PATCH v3 3/5] syscalls/dup2/dup203: Convert to new API QI Fuli
2021-09-16 10:49 ` QI Fuli
2021-09-17 8:16 ` Xiao Yang
2021-09-17 8:16 ` Xiao Yang
2021-09-16 10:49 ` [LTP] [PATCH v3 4/5] syscalls/dup2/dup205: " QI Fuli
2021-09-16 10:49 ` QI Fuli
2021-09-17 8:37 ` Xiao Yang
2021-09-17 8:37 ` Xiao Yang
2021-09-17 9:20 ` qi.fuli
2021-09-17 9:20 ` qi.fuli
2021-09-17 9:59 ` xuyang2018.jy
2021-09-17 9:59 ` xuyang2018.jy
2021-09-16 10:49 ` [LTP] [PATCH v3 5/5] syscalls/dup2: rename dup205 to dup204 QI Fuli
2021-09-16 10:49 ` QI Fuli
2021-09-17 3:20 ` xuyang2018.jy [this message]
2021-09-17 3:20 ` xuyang2018.jy
2021-09-17 4:29 ` qi.fuli
2021-09-17 4:29 ` qi.fuli
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=614409AA.6080809@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=fukuri.sai@gmail.com \
--cc=ltp@lists.linux.it \
--cc=qi.fuli@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.