From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, Sean Young <sean@mess.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, y2038@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/8] media: documentation: fix video_event description
Date: Mon, 16 Dec 2019 16:21:22 +0100 [thread overview]
Message-ID: <20191216162040.6aba340b@kernel.org> (raw)
In-Reply-To: <20191216141506.121728-2-arnd@arndb.de>
Em Mon, 16 Dec 2019 15:14:59 +0100
Arnd Bergmann <arnd@arndb.de> escreveu:
> The type for the timestamp in video_event was changed to
> 'long' a long time ago, change the documentation to match.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
This patch seems fine for me. Even if the other patches need a v7,
let's apply this one and remove it from any future re-spin of this
(if ever needed).
> ---
> Documentation/media/uapi/dvb/video-get-event.rst | 2 +-
> Documentation/media/uapi/dvb/video_types.rst | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/media/uapi/dvb/video-get-event.rst b/Documentation/media/uapi/dvb/video-get-event.rst
> index def6c40db601..7f03fbe3d3b0 100644
> --- a/Documentation/media/uapi/dvb/video-get-event.rst
> +++ b/Documentation/media/uapi/dvb/video-get-event.rst
> @@ -81,7 +81,7 @@ for this ioctl call.
> #define VIDEO_EVENT_FRAME_RATE_CHANGED 2
> #define VIDEO_EVENT_DECODER_STOPPED 3
> #define VIDEO_EVENT_VSYNC 4
> - __kernel_time_t timestamp;
> + long timestamp;
> union {
> video_size_t size;
> unsigned int frame_rate; /* in frames per 1000sec */
> diff --git a/Documentation/media/uapi/dvb/video_types.rst b/Documentation/media/uapi/dvb/video_types.rst
> index 479942ce6fb8..2697400ccf62 100644
> --- a/Documentation/media/uapi/dvb/video_types.rst
> +++ b/Documentation/media/uapi/dvb/video_types.rst
> @@ -170,7 +170,7 @@ VIDEO_GET_EVENT call.
> #define VIDEO_EVENT_FRAME_RATE_CHANGED 2
> #define VIDEO_EVENT_DECODER_STOPPED 3
> #define VIDEO_EVENT_VSYNC 4
> - __kernel_time_t timestamp;
> + long timestamp;
> union {
> video_size_t size;
> unsigned int frame_rate; /* in frames per 1000sec */
Cheers,
Mauro
next prev parent reply other threads:[~2019-12-16 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 14:14 [PATCH v6 0/8] y2038 safety in v4l2 Arnd Bergmann
2019-12-16 14:14 ` [PATCH v6 1/8] media: documentation: fix video_event description Arnd Bergmann
2019-12-16 15:21 ` Mauro Carvalho Chehab [this message]
2019-12-16 14:15 ` [PATCH v6 2/8] media: v4l2: abstract timeval handling in v4l2_buffer Arnd Bergmann
2019-12-16 14:15 ` [PATCH v6 3/8] media: v4l2-core: compat: ignore native command codes Arnd Bergmann
[not found] ` <20191225235522.3516B20727@mail.kernel.org>
2019-12-30 11:15 ` Arnd Bergmann
2019-12-16 14:15 ` [PATCH v6 4/8] media: v4l2-core: split out data copy from video_usercopy Arnd Bergmann
2019-12-16 14:15 ` [PATCH v6 5/8] media: v4l2-core: fix VIDIOC_DQEVENT for time64 ABI Arnd Bergmann
2019-12-16 14:15 ` [PATCH v6 6/8] media: v4l2-core: fix v4l2_buffer handling " Arnd Bergmann
2019-12-16 14:15 ` [PATCH v6 7/8] media: v4l2-core: fix compat VIDIOC_DQEVENT " Arnd Bergmann
2019-12-16 14:15 ` [PATCH v6 8/8] media: v4l2-core: fix compat v4l2_buffer handling " Arnd Bergmann
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=20191216162040.6aba340b@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=arnd@arndb.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sean@mess.org \
--cc=y2038@lists.linaro.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 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.