From: wuchengli@chromium.org (Wu-Cheng Li)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] new control V4L2_CID_MPEG_VIDEO_FORCE_KEY_FRAME
Date: Tue, 19 Jan 2016 15:07:08 +0800 [thread overview]
Message-ID: <1453187230-97231-1-git-send-email-wuchengli@chromium.org> (raw)
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
next reply other threads:[~2016-01-19 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 7:07 Wu-Cheng Li [this message]
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
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
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=1453187230-97231-1-git-send-email-wuchengli@chromium.org \
--to=wuchengli@chromium.org \
--cc=linux-arm-kernel@lists.infradead.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).