All of lore.kernel.org
 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.1] Various fixes
Date: Thu, 31 Jan 2019 15:10:56 +0100	[thread overview]
Message-ID: <c7e9ed04-49c5-3a2d-aecb-98648d0e1ab9@xs4all.nl> (raw)

The following changes since commit 560c053deb94ff65b22a87f28e8e2fab5940555c:

  media: vivid: fix vid_out_buf_prepare() (2019-01-31 09:32:05 -0200)

are available in the Git repository at:

  git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.1k

for you to fetch changes up to 277a309f78411c5c4bc088c72dc19281f53f81a4:

  vicodec: support SOURCE_CHANGE event for decoders only (2019-01-31 15:08:58 +0100)

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

----------------------------------------------------------------
Hans Verkuil (5):
      videobuf2: remove unused variable
      vicodec: check type in g/s_selection
      vicodec: fill in bus_info in media_device_info
      vim2m: fill in bus_info in media_device_info
      vicodec: support SOURCE_CHANGE event for decoders only

Philipp Zabel (1):
      media: imx-pxp: fix duplicated if condition

 drivers/media/common/videobuf2/videobuf2-core.c |  1 -
 drivers/media/platform/imx-pxp.c                |  2 +-
 drivers/media/platform/vicodec/vicodec-core.c   | 18 +++++++++++++++---
 drivers/media/platform/vim2m.c                  |  2 ++
 4 files changed, 18 insertions(+), 5 deletions(-)

             reply	other threads:[~2019-01-31 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 14:10 Hans Verkuil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-18 17:04 [GIT PULL FOR v5.1] Various fixes Hans Verkuil
2019-02-07 15:31 Hans Verkuil
2019-01-16 16:03 Hans Verkuil
2019-01-15  8:16 Hans Verkuil
2019-01-10 12:34 Hans Verkuil
2019-01-10 11:18 Sean Young
2019-01-08 15:44 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=c7e9ed04-49c5-3a2d-aecb-98648d0e1ab9@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 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.