linux-kernel.vger.kernel.org archive mirror
 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 v5.17-rc1] New year's media updates
Date: Sat, 1 Jan 2022 02:29:36 +0100	[thread overview]
Message-ID: <20220101022920.62f31d16@coco.lan> (raw)

Hi Linus,

Since this year the next merge window may happen at the first couple of weeks 
in January, I'm opting to submit the media pull request a little earlier, as
we don't expect too much traffic anyway on media ML, and this might help you
on any travel plans you could have. Also, there's nothing better to desire a
wishful New Year to everybody than to send patches to improve the Linux 
Kernel ;-)

So, please merge from:
  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v5.17-1

For:

  - New sensor driver: ov5693;
  - A new driver for STM32 Chrom-ART Accelerator;
  - Added V4L2 core helper functions for VP9 codec;
  - Hantro driver has gained support for VP9 codecs;
  - Added support for Maxim MAX96712 Quad GMSL2 Deserializer;
  - The staging atomisp driver has gained lots of improvements, fixes
    and cleanups. It now works with userptr;
  - Lots of random driver improvements as usual.

Happy New Year!

Best regards,
Mauro


The following changes since commit 0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1:


Thanks,
Mauro

             reply	other threads:[~2022-01-01  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01  1:29 Mauro Carvalho Chehab [this message]
2022-01-11  3:06 ` [GIT PULL for v5.17-rc1] New year's media updates pr-tracker-bot
2022-01-01  1:42 Mauro Carvalho Chehab
2022-01-03 18:45 ` Nathan Chancellor
2022-01-10 15:07   ` Mauro Carvalho Chehab

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=20220101022920.62f31d16@coco.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;
as well as URLs for NNTP newsgroup(s).