From: "Christian König" <christian.koenig@amd.com>
To: Mukesh Ogare <mukeshogare871@gmail.com>,
alexander.deucher@amd.com, airlied@gmail.com, simona@ffwll.ch,
amd-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/radeon: convert VCE logging to drm_* helpers
Date: Wed, 7 Jan 2026 13:28:29 +0100 [thread overview]
Message-ID: <b6bd1fdd-fae7-4ee9-ae06-9abe168adbd4@amd.com> (raw)
In-Reply-To: <20251220080156.1961026-1-mukeshogare871@gmail.com>
On 12/20/25 09:01, Mukesh Ogare wrote:
> Replace legacy DRM_ERROR() and DRM_INFO() logging in the VCE code
> with drm_err() and drm_info() helpers that take a struct drm_device.
>
> Using drm_* logging provides proper device context in dmesg, which is
> important for systems with multiple DRM devices, and aligns the radeon
> driver with current DRM logging practices.
>
> No functional change intended.
I agree that this should only be info level, but you turn an error level into an info level, so that is a functional change.
Please adjust the commit message accordingly.
Regards,
Christian.
>
> Signed-off-by: Mukesh Ogare <mukeshogare871@gmail.com>
> ---
> drivers/gpu/drm/radeon/radeon_vce.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_vce.c b/drivers/gpu/drm/radeon/radeon_vce.c
> index a203992cb932..fd176034b251 100644
> --- a/drivers/gpu/drm/radeon/radeon_vce.c
> +++ b/drivers/gpu/drm/radeon/radeon_vce.c
> @@ -121,7 +121,7 @@ int radeon_vce_init(struct radeon_device *rdev)
> if (sscanf(c, "%2u]", &rdev->vce.fb_version) != 1)
> return -EINVAL;
>
> - drm_err(&rdev->ddev, "Found VCE firmware/feedback version %d.%d.%d / %d!\n",
> + drm_info(&rdev->ddev, "Found VCE firmware/feedback version %d.%d.%d / %d!\n",
> start, mid, end, rdev->vce.fb_version);
>
> rdev->vce.fw_version = (start << 24) | (mid << 16) | (end << 8);
next prev parent reply other threads:[~2026-01-07 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-20 8:01 Mukesh Ogare
2026-01-07 12:28 ` Christian König [this message]
2026-01-20 6:37 ` [PATCH] " Mukesh Ogare
2026-01-20 15:08 ` Alex Deucher
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=b6bd1fdd-fae7-4ee9-ae06-9abe168adbd4@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukeshogare871@gmail.com \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®