From: Eric Biggers <ebiggers@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: move ioctl interface definitions to separated file
Date: Fri, 30 Oct 2020 09:55:56 -0700 [thread overview]
Message-ID: <20201030165556.GA1097@sol.localdomain> (raw)
In-Reply-To: <20201030072610.57155-1-yuchao0@huawei.com>
On Fri, Oct 30, 2020 at 03:26:10PM +0800, Chao Yu wrote:
> +
> +struct f2fs_gc_range {
> + u32 sync;
> + u64 start;
> + u64 len;
> +};
Userspace headers need to use __u32, __u64, etc. instead of u32, u64, etc.
Did you try installing this header, and including it in a userspace program?
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: move ioctl interface definitions to separated file
Date: Fri, 30 Oct 2020 09:55:56 -0700 [thread overview]
Message-ID: <20201030165556.GA1097@sol.localdomain> (raw)
In-Reply-To: <20201030072610.57155-1-yuchao0@huawei.com>
On Fri, Oct 30, 2020 at 03:26:10PM +0800, Chao Yu wrote:
> +
> +struct f2fs_gc_range {
> + u32 sync;
> + u64 start;
> + u64 len;
> +};
Userspace headers need to use __u32, __u64, etc. instead of u32, u64, etc.
Did you try installing this header, and including it in a userspace program?
- Eric
next prev parent reply other threads:[~2020-10-30 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 7:26 [f2fs-dev] [PATCH v2] f2fs: move ioctl interface definitions to separated file Chao Yu
2020-10-30 7:26 ` Chao Yu
2020-10-30 12:30 ` [f2fs-dev] " Jaegeuk Kim
2020-10-30 12:30 ` Jaegeuk Kim
2020-10-30 15:03 ` [f2fs-dev] " Chao Yu
2020-10-30 15:03 ` Chao Yu
2020-10-30 16:55 ` Eric Biggers [this message]
2020-10-30 16:55 ` [f2fs-dev] " Eric Biggers
2020-10-31 0:32 ` Chao Yu
2020-10-31 0:32 ` Chao Yu
2020-10-30 18:09 ` kernel test robot
2020-10-30 18:09 ` kernel test robot
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=20201030165556.GA1097@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@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.