From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 1/3] drm/xe: Fix RING_MI_MODE label in devcoredump
Date: Wed, 4 Oct 2023 13:11:49 -0400 [thread overview]
Message-ID: <ZR2c1bS4m3W3jeCN@intel.com> (raw)
In-Reply-To: <20231003202728.132545-1-jose.souza@intel.com>
On Tue, Oct 03, 2023 at 01:27:26PM -0700, José Roberto de Souza wrote:
> Fix a typo in RING_MI_MODE label.
>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/xe/xe_hw_engine.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_hw_engine.c b/drivers/gpu/drm/xe/xe_hw_engine.c
> index 49128f640e15d..dc9dd83d99c52 100644
> --- a/drivers/gpu/drm/xe/xe_hw_engine.c
> +++ b/drivers/gpu/drm/xe/xe_hw_engine.c
> @@ -770,7 +770,7 @@ void xe_hw_engine_snapshot_print(struct xe_hw_engine_snapshot *snapshot,
> drm_printf(p, "\tRING_HEAD: 0x%08x\n", snapshot->reg.ring_head);
> drm_printf(p, "\tRING_TAIL: 0x%08x\n", snapshot->reg.ring_tail);
> drm_printf(p, "\tRING_CTL: 0x%08x\n", snapshot->reg.ring_ctl);
> - drm_printf(p, "\tRING_MODE: 0x%08x\n", snapshot->reg.ring_mi_mode);
> + drm_printf(p, "\tRING_MI_MODE: 0x%08x\n", snapshot->reg.ring_mi_mode);
> drm_printf(p, "\tRING_MODE: 0x%08x\n",
> snapshot->reg.ring_mode);
> drm_printf(p, "\tRING_IMR: 0x%08x\n", snapshot->reg.ring_imr);
> --
> 2.42.0
>
prev parent reply other threads:[~2023-10-04 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 20:27 [Intel-xe] [PATCH 1/3] drm/xe: Fix RING_MI_MODE label in devcoredump José Roberto de Souza
2023-10-03 20:27 ` [Intel-xe] [PATCH 2/3] drm/xe: Fix devcoredump readout of IPEHR José Roberto de Souza
2023-10-04 17:10 ` Rodrigo Vivi
2023-10-03 20:27 ` [Intel-xe] [PATCH 3/3] drm/xe: Remove devcoredump readout of IPEIR José Roberto de Souza
2023-10-04 17:11 ` Rodrigo Vivi
2023-10-04 17:15 ` Souza, Jose
2023-10-04 17:32 ` Rodrigo Vivi
2023-10-03 21:14 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe: Fix RING_MI_MODE label in devcoredump Patchwork
2023-10-03 21:14 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-10-03 21:16 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-10-03 21:23 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-03 21:23 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-10-03 21:24 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-10-03 22:02 ` [Intel-xe] ✓ CI.BAT: " Patchwork
2023-10-04 17:11 ` 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=ZR2c1bS4m3W3jeCN@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@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