From: Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
To: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
Cc: linux-api <linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] media: uapi: vsp1: Use __u32 instead of u32
Date: Mon, 18 May 2015 13:30:25 +0300 [thread overview]
Message-ID: <2148994.nAnETH4BnO@avalon> (raw)
In-Reply-To: <1431799900.15709.84.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
Hi Joe,
Thank you for the patch.
On Saturday 16 May 2015 11:11:40 Joe Perches wrote:
> Don't use the kernel types in uapi headers.
>
> Signed-off-by: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
Acked-by: Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
and applied to my tree.
> ---
> include/uapi/linux/vsp1.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/uapi/linux/vsp1.h b/include/uapi/linux/vsp1.h
> index e18858f..9a82369 100644
> --- a/include/uapi/linux/vsp1.h
> +++ b/include/uapi/linux/vsp1.h
> @@ -28,7 +28,7 @@
> _IOWR('V', BASE_VIDIOC_PRIVATE + 1, struct vsp1_lut_config)
>
> struct vsp1_lut_config {
> - u32 lut[256];
> + __u32 lut[256];
> };
>
> #endif /* __VSP1_USER_H__ */
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2015-05-18 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 18:11 [PATCH] media: uapi: vsp1: Use __u32 instead of u32 Joe Perches
[not found] ` <1431799900.15709.84.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2015-05-18 10:30 ` Laurent Pinchart [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=2148994.nAnETH4BnO@avalon \
--to=laurent.pinchart-rylnwiuwjnjg/c1bvhzhaw@public.gmane.org \
--cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).