From: Mauro Carvalho Chehab <mchehab+huawei@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>,
Sebastian Fricke <sebastian.fricke@collabora.com>
Subject: [GIT PULL for v6.13-rc4] media fixes
Date: Sat, 21 Dec 2024 14:20:12 +0100 [thread overview]
Message-ID: <20241221142012.3f43a036@foz.lan> (raw)
Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media.git tags/media/v6.13-3
For:
- a clang build issue with mediatec vcodec:
- a fix at dib3000mb write function missing data init
Regards,
Mauro
---
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media.git tags/media/v6.13-3
for you to fetch changes up to 8b55f8818900c99dd4f55a59a103f5b29e41eb2c:
media: mediatek: vcodec: mark vdec_vp9_slice_map_counts_eob_coef noinline (2024-12-13 17:51:35 +0100)
----------------------------------------------------------------
[GIT PULL for 6.13-rc4] media fixes
----------------------------------------------------------------
Arnd Bergmann (1):
media: mediatek: vcodec: mark vdec_vp9_slice_map_counts_eob_coef noinline
Nikita Zhandarovich (1):
media: dvb-frontends: dib3000mb: fix uninit-value in dib3000_write_reg
drivers/media/dvb-frontends/dib3000mb.c | 2 +-
.../media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_req_lat_if.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2024-12-21 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 13:20 Mauro Carvalho Chehab [this message]
2024-12-21 13:40 ` [GIT PULL for v6.13-rc4] media fixes (#106301) Jenkins
2024-12-21 19:30 ` [GIT PULL for v6.13-rc4] 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=20241221142012.3f43a036@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sebastian.fricke@collabora.com \
--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