linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [GIT PULL FOR v5.5] Various fixes
Date: Sun, 10 Nov 2019 12:21:54 +0100	[thread overview]
Message-ID: <06580f57-7b93-3bfd-7fa5-ad25732f3606@xs4all.nl> (raw)

This is probably the last PR for 5.5.

Regards,

	Hans

The following changes since commit 693c5f144aeb9636ae161a3c61a838c50b2ae41c:

  media: vicodec: media_device_cleanup was called too early (2019-11-10 07:45:17 +0100)

are available in the Git repository at:

  git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.5s

for you to fetch changes up to d18fd7e77774cf3da3e6dc136ad102298434046c:

  media: hantro: Set H264 FIELDPIC_FLAG_E flag correctly (2019-11-10 12:12:28 +0100)

----------------------------------------------------------------
Tag branch

----------------------------------------------------------------
Benoit Parrot (2):
      dt-bindings: media: ti-vpe: Document VPE driver
      media: ti-vpe: vpe: fix compatible to match bindings

Colin Ian King (1):
      media: zr364xx: remove redundant assigmnent to idx, clean up code

Ezequiel Garcia (1):
      media: hantro: Fix s_fmt for dynamic resolution changes

Jonas Karlman (5):
      media: hantro: Fix H264 motion vector buffer offset
      media: hantro: Reduce H264 extra space for motion vectors
      media: hantro: Use output buffer width and height for H264 decoding
      media: hantro: Remove now unused H264 pic_size
      media: hantro: Set H264 FIELDPIC_FLAG_E flag correctly

Nishad Kamdar (2):
      media: siano: Use the correct style for SPDX License Identifier
      media: i2c: Use the correct style for SPDX License Identifier

Ricardo Ribalda Delgado (1):
      Documentation: media: *_DEFAULT targets for subdevs

 Documentation/devicetree/bindings/media/ti,vpe.yaml     | 64 +++++++++++++++++++++++++++++++++++++++++++++
 Documentation/media/uapi/v4l/v4l2-selection-targets.rst |  4 ++-
 MAINTAINERS                                             |  1 +
 drivers/media/common/siano/smsir.h                      |  2 +-
 drivers/media/i2c/max2175.h                             |  4 +--
 drivers/media/i2c/saa711x_regs.h                        |  2 +-
 drivers/media/i2c/tda1997x_regs.h                       |  2 +-
 drivers/media/i2c/tvp5150_reg.h                         |  2 +-
 drivers/media/platform/ti-vpe/vpe.c                     |  2 +-
 drivers/media/usb/zr364xx/zr364xx.c                     |  6 ++---
 drivers/staging/media/hantro/hantro_g1_h264_dec.c       | 37 +++++++++++++++++---------
 drivers/staging/media/hantro/hantro_h264.c              |  5 ----
 drivers/staging/media/hantro/hantro_hw.h                |  3 ---
 drivers/staging/media/hantro/hantro_v4l2.c              | 48 ++++++++++++++++++++++++++--------
 14 files changed, 139 insertions(+), 43 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/media/ti,vpe.yaml

             reply	other threads:[~2019-11-10 11:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 11:21 Hans Verkuil [this message]
2019-11-10 11:36 ` [GIT PULL FOR v5.5] Various fixes Jenkins

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=06580f57-7b93-3bfd-7fa5-ad25732f3606@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linux-media@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).