From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: linux-media@vger.kernel.org
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: [GIT PULL FOR 6.17] Media Codec Fixes 2025-08-12
Date: Tue, 12 Aug 2025 16:31:22 -0400 [thread overview]
Message-ID: <d5a7552c0c19902259931fa5002eda09b5e88dbb.camel@collabora.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Hey Mauro,
This includes two fixes for issues reported against in 6.17-rc1 in rkvdec driver
along with a removal of pm_runtime_mark_last_busy() requested by Sakari. This is
my first pull request against "fixes", let me know if this is appropriate.
cheers,
Nicolas
---
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://gitlab.freedesktop.org/linux-media/users/ndufresne.git tags/fixes-for-6.17-media-codecs-2025-08-12
for you to fetch changes up to 85cb7dc3d2415685a4372f637cf26e5f077e6842:
media: rkvdec: Remove redundant pm_runtime_mark_last_busy() calls (2025-08-11 16:32:26 -0400)
----------------------------------------------------------------
rkvdec 6.17-rc1 introduced bugs and PM runtime cleanup
----------------------------------------------------------------
Christophe JAILLET (1):
media: rkvdec: Fix an error handling path in rkvdec_probe()
Dan Carpenter (1):
media: rkvdec: Fix a NULL vs IS_ERR() bug in probe()
Sakari Ailus (1):
media: rkvdec: Remove redundant pm_runtime_mark_last_busy() calls
drivers/media/platform/rockchip/rkvdec/rkvdec.c | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2025-08-12 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 20:31 Nicolas Dufresne [this message]
2025-08-12 21:08 ` [GIT PULL FOR 6.17] Media Codec Fixes 2025-08-12 Nicolas Dufresne
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=d5a7552c0c19902259931fa5002eda09b5e88dbb.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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