From: Hans Verkuil <hverkuil@xs4all.nl>
To: "Wu-Cheng Li (李務誠)" <wuchengli@chromium.org>
Cc: pawel@osciak.com, mchehab@osg.samsung.com, k.debski@samsung.com,
Antti Palosaari <crope@iki.fi>,
Masanari Iida <standby24x7@gmail.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
ao2@ao2.it, bparrot@ti.com,
Kyungmin Park <kyungmin.park@samsung.com>,
jtp.park@samsung.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tiffany Lin <tiffany.lin@mediatek.com>,
Daniel Kurtz <djkurtz@chromium.org>
Subject: Re: [PATCH v4 0/2] new control V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME
Date: Mon, 25 Jan 2016 09:57:53 +0100 [thread overview]
Message-ID: <56A5E391.8050505@xs4all.nl> (raw)
In-Reply-To: <CAOMLVLh7EnMgVfzV7JQy6DSKSaanqHn5kNkTLVrbTCihjphzYA@mail.gmail.com>
On 01/25/2016 05:46 AM, Wu-Cheng Li (李務誠) wrote:
> Hi Hans,
> Can you look at the patch again? I've changed the name from
> V4L2_CID_MPEG_VIDEO_FORCE_I_FRAME to
> V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME. Thanks.
Looks good to me. I'm planning to make a pull request for this once v4.5-rc1 is
merged into our media_tree repo.
Regards,
Hans
>
> Wu-Cheng
>
> On Tue, Jan 19, 2016 at 3:07 PM, Wu-Cheng Li <wuchengli@chromium.org> wrote:
>> v4 changes:
>> - Change the name to V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME.
>> - Add commit message to s5p-mfc patch.
>>
>> Wu-Cheng Li (2):
>> v4l: add V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME.
>> s5p-mfc: add the support of V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME.
>>
>> Documentation/DocBook/media/v4l/controls.xml | 8 ++++++++
>> drivers/media/platform/s5p-mfc/s5p_mfc_enc.c | 12 ++++++++++++
>> drivers/media/v4l2-core/v4l2-ctrls.c | 2 ++
>> include/uapi/linux/v4l2-controls.h | 1 +
>> 4 files changed, 23 insertions(+)
>>
>> --
>> 2.6.0.rc2.230.g3dd15c0
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-01-25 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 7:07 [PATCH v4 0/2] new control V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME Wu-Cheng Li
2016-01-19 7:07 ` [PATCH v4 1/2] v4l: add V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME Wu-Cheng Li
2016-01-19 7:07 ` [PATCH v4 2/2] s5p-mfc: add the support of V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME Wu-Cheng Li
[not found] ` <1453187230-97231-3-git-send-email-wuchengli-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-02-16 10:29 ` Sylwester Nawrocki
2016-01-25 4:46 ` [PATCH v4 0/2] new control V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME Wu-Cheng Li (李務誠)
2016-01-25 8:57 ` Hans Verkuil [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=56A5E391.8050505@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=ao2@ao2.it \
--cc=bparrot@ti.com \
--cc=crope@iki.fi \
--cc=djkurtz@chromium.org \
--cc=jtp.park@samsung.com \
--cc=k.debski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=nicolas.dufresne@collabora.com \
--cc=pawel@osciak.com \
--cc=ricardo.ribalda@gmail.com \
--cc=standby24x7@gmail.com \
--cc=tiffany.lin@mediatek.com \
--cc=wuchengli@chromium.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).