From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc/rc: Use i915_probe_error instead of drm_error
Date: Fri, 13 May 2022 17:16:26 +0000 [thread overview]
Message-ID: <b8f729f5f04adf6203c192b9226fc80ffb53a6d3.camel@intel.com> (raw)
In-Reply-To: <20220506054142.5025-1-vinay.belgaumkar@intel.com>
Nit: not sure why we use ERR_PTR for int when calling func was also returning an int.
Anyway, that was how the original code was, so:
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
On Thu, 2022-05-05 at 22:41 -0700, Vinay Belgaumkar wrote:
> To avoid false positives in error injection cases.
>
> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_rc.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_rc.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_rc.c
> index e00661fb0853..8f8dd05835c5 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_rc.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_rc.c
> @@ -49,7 +49,6 @@ static int guc_action_control_gucrc(struct intel_guc *guc, bool enable)
> static int __guc_rc_control(struct intel_guc *guc, bool enable)
> {
> struct intel_gt *gt = guc_to_gt(guc);
> - struct drm_device *drm = &guc_to_gt(guc)->i915->drm;
> int ret;
>
> if (!intel_uc_uses_guc_rc(>->uc))
> @@ -60,8 +59,8 @@ static int __guc_rc_control(struct intel_guc *guc, bool enable)
>
> ret = guc_action_control_gucrc(guc, enable);
> if (ret) {
> - drm_err(drm, "Failed to %s GuC RC (%pe)\n",
> - str_enable_disable(enable), ERR_PTR(ret));
> + i915_probe_error(guc_to_gt(guc)->i915, "Failed to %s GuC RC (%pe)\n",
> + str_enable_disable(enable), ERR_PTR(ret));
> return ret;
> }
>
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-05-13 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 5:41 [Intel-gfx] [PATCH] drm/i915/guc/rc: Use i915_probe_error instead of drm_error Vinay Belgaumkar
2022-05-06 7:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-05-06 9:27 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-05-13 17:16 ` Teres Alexis, Alan Previn [this message]
2022-05-16 8:09 ` [Intel-gfx] [PATCH] " Jani Nikula
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=b8f729f5f04adf6203c192b9226fc80ffb53a6d3.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vinay.belgaumkar@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