From: Oded Gabbay <oded.gabbay@gmail.com>
To: Felix Kuehling <Felix.Kuehling@amd.com>,
"Shaoyun.liu" <shaoyun.liu@amd.com>,
Jay Cornwall <Jay.Cornwall@amd.com>,
Oded Gabbay <oded.gabbay@gmail.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] uapi: fix linux/kfd_ioctl.h userspace compilation errors
Date: Tue, 24 Apr 2018 12:32:24 +0300 [thread overview]
Message-ID: <CAFCwf114E=JV--VuNGEcrgDYVYMF1H+5Qe-ukiWYcfjq9ie0Qw@mail.gmail.com> (raw)
In-Reply-To: <20180405042655.GA13233@altlinux.org>
Thanks, but already fixed in latest upstream tree
Oded
On Thu, Apr 5, 2018 at 7:26 AM, Dmitry V. Levin <ldv@altlinux.org> wrote:
> Consistently use types provided by <linux/types.h> via <drm/drm.h>
> to fix the following linux/kfd_ioctl.h userspace compilation errors:
>
> /usr/include/linux/kfd_ioctl.h:266:2: error: unknown type name 'uint64_t'
> uint64_t tba_addr; /* to KFD */
> /usr/include/linux/kfd_ioctl.h:267:2: error: unknown type name 'uint64_t'
> uint64_t tma_addr; /* to KFD */
> /usr/include/linux/kfd_ioctl.h:268:2: error: unknown type name 'uint32_t'
> uint32_t gpu_id; /* to KFD */
> /usr/include/linux/kfd_ioctl.h:269:2: error: unknown type name 'uint32_t'
> uint32_t pad;
>
> Fixes: d7b9bd2248d79 ("drm/amdkfd: Add support for user-mode trap handlers")
> Cc: <stable@vger.kernel.org> # v4.16
> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
> ---
> include/uapi/linux/kfd_ioctl.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/uapi/linux/kfd_ioctl.h b/include/uapi/linux/kfd_ioctl.h
> index f4cab5b3ba9a..111d73ba2d96 100644
> --- a/include/uapi/linux/kfd_ioctl.h
> +++ b/include/uapi/linux/kfd_ioctl.h
> @@ -263,10 +263,10 @@ struct kfd_ioctl_get_tile_config_args {
> };
>
> struct kfd_ioctl_set_trap_handler_args {
> - uint64_t tba_addr; /* to KFD */
> - uint64_t tma_addr; /* to KFD */
> - uint32_t gpu_id; /* to KFD */
> - uint32_t pad;
> + __u64 tba_addr; /* to KFD */
> + __u64 tma_addr; /* to KFD */
> + __u32 gpu_id; /* to KFD */
> + __u32 pad;
> };
>
> #define AMDKFD_IOCTL_BASE 'K'
> --
> ldv
next prev parent reply other threads:[~2018-04-24 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 4:26 [PATCH] uapi: fix linux/kfd_ioctl.h userspace compilation errors Dmitry V. Levin
2018-04-09 3:36 ` Sasha Levin
2018-04-24 9:32 ` Oded Gabbay [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-13 0:35 Dmitry V. Levin
2017-11-13 16:11 ` Oded Gabbay
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='CAFCwf114E=JV--VuNGEcrgDYVYMF1H+5Qe-ukiWYcfjq9ie0Qw@mail.gmail.com' \
--to=oded.gabbay@gmail.com \
--cc=Felix.Kuehling@amd.com \
--cc=Jay.Cornwall@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaoyun.liu@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).