From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <jani.nikula@linux.intel.com>,
<joonas.lahtinen@linux.intel.com>, <tursulin@ursulin.net>,
<airlied@gmail.com>, <simona@ffwll.ch>,
<alok.a.tiwarilinux@gmail.com>
Subject: Re: [PATCH next] drm/i915/dmc: Fix extra bracket and wrong variable in PIPEDMC error logs
Date: Wed, 5 Nov 2025 14:36:15 -0500 [thread overview]
Message-ID: <aQunL66v3HLWAMEo@intel.com> (raw)
In-Reply-To: <20251103132337.762156-1-alok.a.tiwari@oracle.com>
On Mon, Nov 03, 2025 at 05:23:31AM -0800, Alok Tiwari wrote:
> Fixes two issues in intel_pipedmc_irq_handler():
> - Removed an extra ']' in the PIPEDMC error and interrupt vector log.
> - Corrected the interrupt vector log to print int_vector instead of tmp,
> as tmp will be zero in this case.
>
> Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
and pushed to drm-intel-next
thanks for the patch
---
> drivers/gpu/drm/i915/display/intel_dmc.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dmc.c b/drivers/gpu/drm/i915/display/intel_dmc.c
> index 0bddb20a7c86..f47b57568a75 100644
> --- a/drivers/gpu/drm/i915/display/intel_dmc.c
> +++ b/drivers/gpu/drm/i915/display/intel_dmc.c
> @@ -1712,14 +1712,14 @@ void intel_pipedmc_irq_handler(struct intel_display *display, enum pipe pipe)
> drm_err_ratelimited(display->drm, "[CRTC:%d:%s] PIPEDMC GTT fault\n",
> crtc->base.base.id, crtc->base.name);
> if (tmp & PIPEDMC_ERROR)
> - drm_err(display->drm, "[CRTC:%d:%s]] PIPEDMC error\n",
> + drm_err(display->drm, "[CRTC:%d:%s] PIPEDMC error\n",
> crtc->base.base.id, crtc->base.name);
> }
>
> int_vector = intel_de_read(display, PIPEDMC_STATUS(pipe)) & PIPEDMC_INT_VECTOR_MASK;
> if (tmp == 0 && int_vector != 0)
> - drm_err(display->drm, "[CRTC:%d:%s]] PIPEDMC interrupt vector 0x%x\n",
> - crtc->base.base.id, crtc->base.name, tmp);
> + drm_err(display->drm, "[CRTC:%d:%s] PIPEDMC interrupt vector 0x%x\n",
> + crtc->base.base.id, crtc->base.name, int_vector);
> }
>
> void intel_pipedmc_enable_event(struct intel_crtc *crtc,
> --
> 2.50.1
>
prev parent reply other threads:[~2025-11-05 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 13:23 [PATCH next] drm/i915/dmc: Fix extra bracket and wrong variable in PIPEDMC error logs Alok Tiwari
2025-11-03 13:31 ` ✓ CI.KUnit: success for " Patchwork
2025-11-03 14:36 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-03 15:51 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-05 19:36 ` Rodrigo Vivi [this message]
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=aQunL66v3HLWAMEo@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=alok.a.tiwari@oracle.com \
--cc=alok.a.tiwarilinux@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
/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).