The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL for v6.1] media fixes
Date: Fri, 9 Dec 2022 18:41:29 +0000	[thread overview]
Message-ID: <20221209184129.1fdf3973@sal.lan> (raw)

Hi Linus,

Please pull from:
  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.1-4

For a v4l-core fix related to validating DV timings related to video
blanking values.

Thanks!
Mauro

---

The following changes since commit de547896aac606a00435a219757a940ece142bf0:

  media: vivid.rst: loop_video is set on the capture devnode (2022-10-25 16:43:54 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.1-4

for you to fetch changes up to 5eef2141776da02772c44ec406d6871a790761ee:

  media: v4l2-dv-timings.c: fix too strict blanking sanity checks (2022-11-23 12:02:30 +0000)

----------------------------------------------------------------
media fixes for v6.1-rc9

----------------------------------------------------------------
Hans Verkuil (1):
      media: v4l2-dv-timings.c: fix too strict blanking sanity checks

 drivers/media/v4l2-core/v4l2-dv-timings.c | 20 ++++++++++++++------
 1 file changed, 14 insertions(+), 6 deletions(-)


             reply	other threads:[~2022-12-09 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 18:41 Mauro Carvalho Chehab [this message]
2022-12-09 18:54 ` [GIT PULL for v6.1] media fixes pr-tracker-bot

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=20221209184129.1fdf3973@sal.lan \
    --to=mchehab@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=torvalds@linux-foundation.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