stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: gregkh@linuxfoundation.org
Cc: Felix.Kuehling@amd.com, alexander.deucher@amd.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] uapi: fix linux/kfd_ioctl.h userspace compilation errors" failed to apply to 4.19-stable tree
Date: Sat, 5 Jan 2019 21:09:09 +0300	[thread overview]
Message-ID: <20190105180909.GA10546@altlinux.org> (raw)
In-Reply-To: <154670729512456@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

Hi,

On Sat, Jan 05, 2019 at 05:54:55PM +0100, gregkh@linuxfoundation.org wrote:
> 
> The patch below does not apply to the 4.19-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
> 
> thanks,
> 
> greg k-h

This patch has already been applied to the 4.19-stable tree
as commit id v4.19.3~55 (0d406e7972dd47c54959281782e05f52c8a10c95).

Thanks,

> ------------------ original commit in Linus's tree ------------------
> 
> >From 9349e23907be1954ccdf6d771d640e2788da1643 Mon Sep 17 00:00:00 2001
> From: "Dmitry V. Levin" <ldv@altlinux.org>
> Date: Thu, 1 Nov 2018 14:03:08 +0300
> Subject: [PATCH] uapi: fix linux/kfd_ioctl.h userspace compilation errors
> 
> 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:250:2: error: unknown type name 'uint32_t'
>   uint32_t reset_type;
> /usr/include/linux/kfd_ioctl.h:251:2: error: unknown type name 'uint32_t'
>   uint32_t reset_cause;
> /usr/include/linux/kfd_ioctl.h:252:2: error: unknown type name 'uint32_t'
>   uint32_t memory_lost;
> /usr/include/linux/kfd_ioctl.h:253:2: error: unknown type name 'uint32_t'
>   uint32_t gpu_id;
> 
> Fixes: 0c119abad7f0d ("drm/amd: Add kfd ioctl defines for hw_exception event")
> Cc: <stable@vger.kernel.org> # v4.19
> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
> Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> 
> diff --git a/include/uapi/linux/kfd_ioctl.h b/include/uapi/linux/kfd_ioctl.h
> index f5ff8a76e208..dae897f38e59 100644
> --- a/include/uapi/linux/kfd_ioctl.h
> +++ b/include/uapi/linux/kfd_ioctl.h
> @@ -255,10 +255,10 @@ struct kfd_hsa_memory_exception_data {
>  
>  /* hw exception data */
>  struct kfd_hsa_hw_exception_data {
> -	uint32_t reset_type;
> -	uint32_t reset_cause;
> -	uint32_t memory_lost;
> -	uint32_t gpu_id;
> +	__u32 reset_type;
> +	__u32 reset_cause;
> +	__u32 memory_lost;
> +	__u32 gpu_id;
>  };
>  
>  /* Event data */

-- 
ldv

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

      reply	other threads:[~2019-01-05 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05 16:54 FAILED: patch "[PATCH] uapi: fix linux/kfd_ioctl.h userspace compilation errors" failed to apply to 4.19-stable tree gregkh
2019-01-05 18:09 ` Dmitry V. Levin [this message]

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=20190105180909.GA10546@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=Felix.Kuehling@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    /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).