All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Raag Jadav" <raag.jadav@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 5/5] drm/xe/wedge: Update naming to match with xe_wedge
Date: Mon, 31 Aug 2026 04:35:23 +0000	[thread overview]
Message-ID: <20260831043523.CC9B81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831042633.1760474-6-raag.jadav@intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The function `xe_device_wedged` was renamed to `xe_wedged` across the codebase, but the call sites in `drivers/gpu/drm/xe/xe_guc_pc.c` were missed. This will cause an implicit function declaration error and break the build.
--

commit 0a6019f57c4cdf740c1b6783f7839f86d0fd9f5c
Author: Raag Jadav <raag.jadav@intel.com>

drm/xe/wedge: Update naming to match with xe_wedge
    
Now that we have a dedicated xe_wedge component, update all its function
names accordingly.

> diff --git a/drivers/gpu/drm/xe/xe_wedge.c b/drivers/gpu/drm/xe/xe_wedge.c
> index 04d8c5666be14..5982ea7e0f573 100644
> --- a/drivers/gpu/drm/xe/xe_wedge.c
> +++ b/drivers/gpu/drm/xe/xe_wedge.c
[ ... ]
> @@ -54,24 +54,24 @@
>   */
>  
>  /**
> - * xe_device_set_wedged_method() - Set wedge recovery method
> + * xe_wedge_set_method() - Set wedge recovery method
>   * @xe: xe device instance
>   * @method: recovery method to set
>   *
>   * Set wedge recovery method to be sent in drm wedged uevent.
>   */
> -void xe_device_set_wedged_method(struct xe_device *xe, unsigned long method)
> +void xe_wedge_set_method(struct xe_device *xe, unsigned long method)
>  {
>  	xe->wedged.method = method;
>  }
>  
>  /**
> - * xe_device_wedged() - Check for wedged device
> + * xe_wedged() - Check for wedged device
>   * @xe: xe device instance
>   *
>   * Returns: %true if device is wedged, %false otherwise.
>   */
> -bool xe_device_wedged(struct xe_device *xe)
> +bool xe_wedged(struct xe_device *xe)
>  {
>  	return atomic_read(&xe->wedged.flag);
>  }

[Severity: Low]
Does this rename break the build by missing call sites in
drivers/gpu/drm/xe/xe_guc_pc.c?

Looking at xe_guc_pc.c, it seems xe_device_wedged() is still being called in
several places:

drivers/gpu/drm/xe/xe_guc_pc.c:pc_action_reset() {
	...
	ret = xe_guc_ct_send(ct, action, ARRAY_SIZE(action), 0, 0);
	if (ret && !(xe_device_wedged(pc_to_xe(pc)) && ret == -ECANCELED))
		xe_gt_err(pc_to_gt(pc), "GuC PC reset failed: %pe\n",
			  ERR_PTR(ret));
	...
}

Similar missed renames exist in pc_action_query_task_state(),
pc_action_set_param(), pc_action_unset_param(), and xe_guc_pc_fini_hw().

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260831042633.1760474-1-raag.jadav@intel.com?part=5

  reply	other threads:[~2026-08-31  4:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  4:25 [PATCH v2 0/5] Introduce xe_wedge Raag Jadav
2026-08-31  4:25 ` [PATCH v2 1/5] drm/xe/gt: Use GT ordered workqueue for wedging Raag Jadav
2026-08-31  4:25 ` [PATCH v2 2/5] drm/xe: Make xe_device_declare_wedged() IRQ safe Raag Jadav
2026-08-31  4:40   ` sashiko-bot
2026-08-31  4:25 ` [PATCH v2 3/5] drm/xe: Introduce xe_wedge Raag Jadav
2026-09-02 17:56   ` Rodrigo Vivi
2026-08-31  4:25 ` [PATCH v2 4/5] drm/xe/debugfs: Consolidate wedged_mode debt into xe_wedge Raag Jadav
2026-09-07  7:24   ` Laguna, Lukasz
2026-09-07  7:53     ` Raag Jadav
2026-09-07  8:40       ` Laguna, Lukasz
2026-08-31  4:25 ` [PATCH v2 5/5] drm/xe/wedge: Update naming to match with xe_wedge Raag Jadav
2026-08-31  4:35   ` sashiko-bot [this message]
2026-08-31  4:33 ` ✗ CI.checkpatch: warning for Introduce xe_wedge Patchwork
2026-08-31  4:34 ` ✗ CI.KUnit: 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=20260831043523.CC9B81F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=raag.jadav@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.