All of lore.kernel.org
 help / color / mirror / Atom feed
From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: wenyehai <wenyehai@huawei.com>
Cc: wenyehai via ltp <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] bugfix for vmsplice/vmsplice02.c
Date: Wed, 1 Dec 2021 01:07:26 +0000	[thread overview]
Message-ID: <61A6CAD9.8030102@fujitsu.com> (raw)
In-Reply-To: <1637972238-105160-1-git-send-email-wenyehai@huawei.com>

Hi wen
> vmsplice/vmsplice02: Remove duplicate header files fcntl.h.
>
> Signed-off-by: Yehai Wen<wenyehai@huawei.com>
> ---
>   testcases/kernel/syscalls/vmsplice/vmsplice02.c | 1 -
>   1 file changed, 1 deletion(-)
>
> diff --git a/testcases/kernel/syscalls/vmsplice/vmsplice02.c b/testcases/kernel/syscalls/vmsplice/vmsplice02.c
> index 39c407c..3dc623f 100644
> --- a/testcases/kernel/syscalls/vmsplice/vmsplice02.c
> +++ b/testcases/kernel/syscalls/vmsplice/vmsplice02.c
> @@ -20,7 +20,6 @@
>   #include<sys/stat.h>
>   #include<fcntl.h>
>   #include<unistd.h>
> -#include<fcntl.h>
>   #include<sys/uio.h>
>   #include<limits.h>
Actually, lapi/fcntl.h has included fcntl.h, so the latter fcnlt.h also 
can be removed.

It looks ltp other places also exist this duplicate header files fcntl.h 
because of lapi/fcntl.h. I think we should remove fcntl.h for these 
cases when them use lapi/fcntl.h.

You can use "git grep "fcntl.h" " cmd to search them.


Best Regards
Yang Xu
>

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2021-12-01  1:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27  0:17 [LTP] [PATCH] bugfix for vmsplice/vmsplice02.c wenyehai via ltp
2021-12-01  1:07 ` xuyang2018.jy [this message]
2021-12-02 11:43   ` [LTP] 答复: " wenyehai via ltp
  -- strict thread matches above, loose matches on Subject: below --
2021-11-27  2:39 [LTP] " wenyehai via ltp

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=61A6CAD9.8030102@fujitsu.com \
    --to=xuyang2018.jy@fujitsu.com \
    --cc=ltp@lists.linux.it \
    --cc=wenyehai@huawei.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.