From: llyyr via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: llyyr <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] avutil/hwcontext_d3d12va: use hwdev context for logging (PR #21044)
Date: Sat, 29 Nov 2025 11:38:12 -0000
Message-ID: <176441629289.39.14046835927703367131@2cb04c0e5124> (raw)
PR #21044 opened by llyyr
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21044
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21044.patch
This fixes warning about av_log being called with NULL AVClass.
>From 63fd8b6c7daf554a3fcf7de5cedf097873bf8537 Mon Sep 17 00:00:00 2001
From: llyyr <llyyr.public@gmail.com>
Date: Sat, 29 Nov 2025 17:03:17 +0530
Subject: [PATCH] avutil/hwcontext_d3d12va: use hwdev context for logging
This fixes warning about av_log being called with NULL AVClass.
---
libavutil/hwcontext_d3d12va.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavutil/hwcontext_d3d12va.c b/libavutil/hwcontext_d3d12va.c
index b80227b56c..164f15a285 100644
--- a/libavutil/hwcontext_d3d12va.c
+++ b/libavutil/hwcontext_d3d12va.c
@@ -746,7 +746,7 @@ static int d3d12va_device_create(AVHWDeviceContext *hwdev, const char *device,
DXGI_ADAPTER_DESC desc;
hr = IDXGIAdapter2_GetDesc(pAdapter, &desc);
if (!FAILED(hr)) {
- av_log(ctx, AV_LOG_INFO, "Using device %04x:%04x (%ls).\n",
+ av_log(hwdev, AV_LOG_INFO, "Using device %04x:%04x (%ls).\n",
desc.VendorId, desc.DeviceId, desc.Description);
}
}
@@ -754,7 +754,7 @@ static int d3d12va_device_create(AVHWDeviceContext *hwdev, const char *device,
hr = priv->create_device((IUnknown *)pAdapter, D3D_FEATURE_LEVEL_12_0, &IID_ID3D12Device, (void **)&ctx->device);
D3D12_OBJECT_RELEASE(pAdapter);
if (FAILED(hr)) {
- av_log(ctx, AV_LOG_ERROR, "Failed to create Direct 3D 12 device (%lx)\n", (long)hr);
+ av_log(hwdev, AV_LOG_ERROR, "Failed to create Direct 3D 12 device (%lx)\n", (long)hr);
return AVERROR_UNKNOWN;
}
}
--
2.49.1
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-11-29 11:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=176441629289.39.14046835927703367131@2cb04c0e5124 \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git