From: sashiko-bot@kernel.org
To: "Dnyaneshwar Bhadane" <dnyaneshwar.bhadane@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v7 05/12] drm/xe/memirq: Report errors using structured xe_log API
Date: Mon, 12 Oct 2026 12:31:57 +0000 [thread overview]
Message-ID: <sashiko-outbox-168106@kernel.org> (raw)
In-Reply-To: <20261012122522.2307625-6-dnyaneshwar.bhadane@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] deadcode: unused memirq_err macro left in file
--
commit c32c066b460938805d748f9376a0c96a69f7328b
Author: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
drm/xe/memirq: Report errors using structured xe_log API
This commit replaces memirq_err calls with xe_log_err to report errors using
the structured xe_log API. It updates the error logging in memirq_alloc_pages
and xe_memirq_init_guc to use the new format.
> diff --git a/drivers/gpu/drm/xe/xe_memirq.c b/drivers/gpu/drm/xe/xe_memirq.c
> index 9dfe965cb46ec..32b9f87a10ecf 100644
> --- a/drivers/gpu/drm/xe/xe_memirq.c
> +++ b/drivers/gpu/drm/xe/xe_memirq.c
[ ... ]
> @@ -232,7 +233,7 @@ static int memirq_alloc_pages(struct xe_memirq *memirq)
> return 0;
>
> out:
> - memirq_err(memirq, "Failed to allocate memirq page (%pe)\n", ERR_PTR(err));
> + xe_log_err(tile, MEMIRQ, err, "Failed to allocate memirq page\n");
[Severity: Low]
Since this patch completely replaces all invocations of memirq_err with
xe_log_err, could we also remove the memirq_err macro definition from
drivers/gpu/drm/xe/xe_memirq.c to avoid leaving unused code?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261012122522.2307625-1-dnyaneshwar.bhadane@intel.com?part=5
next prev parent reply other threads:[~2026-10-12 12:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 12:25 [PATCH v7 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-10-12 12:31 ` sashiko-bot [this message]
2026-10-12 12:25 ` [PATCH v7 06/12] drm/xe/reg_sr: Report save-restore " Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 07/12] drm/xe/pat: Return error from xe_pat_init_early() on unknown platform Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 08/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 09/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 10/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 11/12] drm/xe/vram: Report tile vs device VRAM visibility errors Dnyaneshwar Bhadane
2026-10-12 12:25 ` [PATCH v7 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-12 13:23 ` Mallesh, Koujalagi
2026-10-12 18:04 ` ✓ CI.KUnit: success for drm/xe: Convert IO_BUS errors to structured xe_log API (rev8) Patchwork
2026-10-12 21:03 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-13 2:57 ` ✗ Xe.CI.FULL: failure " Patchwork
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=sashiko-outbox-168106@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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