Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Print return value on error
Date: Mon, 17 Oct 2022 08:11:11 +0200	[thread overview]
Message-ID: <6c421a02-5aa5-db5e-8eac-6ebfc5cbc8d9@intel.com> (raw)
In-Reply-To: <20221014154655.14075-1-nirmoy.das@intel.com>

On 14.10.2022 17:46, Nirmoy Das wrote:
> Print returned error code for better debuggability.
> 
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/7211
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>

Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>

Regards
Andrzej

> ---
>   drivers/gpu/drm/i915/display/intel_fbdev.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_fbdev.c b/drivers/gpu/drm/i915/display/intel_fbdev.c
> index 112aa0447a0d..ab385d18ddcc 100644
> --- a/drivers/gpu/drm/i915/display/intel_fbdev.c
> +++ b/drivers/gpu/drm/i915/display/intel_fbdev.c
> @@ -175,7 +175,7 @@ static int intelfb_alloc(struct drm_fb_helper *helper,
>   	}
>   
>   	if (IS_ERR(obj)) {
> -		drm_err(&dev_priv->drm, "failed to allocate framebuffer\n");
> +		drm_err(&dev_priv->drm, "failed to allocate framebuffer (%pe)\n", obj);
>   		return PTR_ERR(obj);
>   	}
>   
> @@ -256,7 +256,7 @@ static int intelfb_create(struct drm_fb_helper *helper,
>   
>   	info = drm_fb_helper_alloc_fbi(helper);
>   	if (IS_ERR(info)) {
> -		drm_err(&dev_priv->drm, "Failed to allocate fb_info\n");
> +		drm_err(&dev_priv->drm, "Failed to allocate fb_info (%pe)\n", info);
>   		ret = PTR_ERR(info);
>   		goto out_unpin;
>   	}
> @@ -291,7 +291,7 @@ static int intelfb_create(struct drm_fb_helper *helper,
>   	vaddr = i915_vma_pin_iomap(vma);
>   	if (IS_ERR(vaddr)) {
>   		drm_err(&dev_priv->drm,
> -			"Failed to remap framebuffer into virtual memory\n");
> +			"Failed to remap framebuffer into virtual memory (%pe)\n", vaddr);
>   		ret = PTR_ERR(vaddr);
>   		goto out_unpin;
>   	}


  parent reply	other threads:[~2022-10-17  6:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 15:46 [Intel-gfx] [PATCH v2] drm/i915: Print return value on error Nirmoy Das
2022-10-14 17:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Print return value on error (rev2) Patchwork
2022-10-14 19:01 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-10-17  6:11 ` Andrzej Hajda [this message]
2022-10-18 13:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Print return value on error (rev3) Patchwork
2022-10-19 10:26 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=6c421a02-5aa5-db5e-8eac-6ebfc5cbc8d9@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nirmoy.das@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