From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/3] Build fix undefined struct file_handle
Date: Wed, 13 Jan 2021 10:23:46 +0800 [thread overview]
Message-ID: <5FFE59B2.1040903@cn.fujitsu.com> (raw)
In-Reply-To: <20210112193039.12506-1-pvorel@suse.cz>
Hi Petr
I think detecting file_handle struct(it is in fcntl.h) in configure.ac
is correct instead of using HAVE_NAME_TO_HANDLE_AT macro directly.
Best Regards
Yang Xu
> Hi all,
>
> this would be great to get merged before release.
>
> Kind regards,
> Petr
>
> Petr Vorel (3):
> lapi: Move struct file_handle into lapi/fcntl.h
> fanotify: Fix build on undefined struct file_handle
> syscalls: Remove unused include<fcntl.h>
>
> include/lapi/fcntl.h | 10 ++++++++++
> include/lapi/name_to_handle_at.h | 9 +--------
> testcases/kernel/syscalls/fanotify/fanotify.h | 2 +-
> testcases/kernel/syscalls/fanotify/fanotify09.c | 1 -
> testcases/kernel/syscalls/fanotify/fanotify13.c | 1 -
> testcases/kernel/syscalls/fanotify/fanotify15.c | 1 -
> testcases/kernel/syscalls/fanotify/fanotify16.c | 1 -
> .../syscalls/name_to_handle_at/name_to_handle_at01.c | 1 -
> .../syscalls/name_to_handle_at/name_to_handle_at02.c | 1 -
> .../syscalls/open_by_handle_at/open_by_handle_at01.c | 1 -
> .../syscalls/open_by_handle_at/open_by_handle_at02.c | 1 -
> 11 files changed, 12 insertions(+), 17 deletions(-)
>
next prev parent reply other threads:[~2021-01-13 2:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 19:30 [LTP] [PATCH 0/3] Build fix undefined struct file_handle Petr Vorel
2021-01-12 19:30 ` [LTP] [PATCH 1/3] lapi: Move struct file_handle into lapi/fcntl.h Petr Vorel
2021-01-12 19:30 ` [LTP] [PATCH 2/3] fanotify: Fix build on undefined struct file_handle Petr Vorel
2021-01-12 19:30 ` [LTP] [PATCH 3/3] syscalls: Remove unused include <fcntl.h> Petr Vorel
2021-01-13 2:23 ` Yang Xu [this message]
2021-01-13 6:33 ` [LTP] [PATCH 0/3] Build fix undefined struct file_handle Petr Vorel
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=5FFE59B2.1040903@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--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 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.