All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	John Harrison <John.C.Harrison@intel.com>
Subject: Re: [PATCH] drm/xe/pxp: Don't use 0 to indicate NULL
Date: Tue, 4 Feb 2025 17:52:52 -0500	[thread overview]
Message-ID: <Z6KaRFxc3iV9JqlN@intel.com> (raw)
In-Reply-To: <20250204200144.1445800-1-daniele.ceraolospurio@intel.com>

On Tue, Feb 04, 2025 at 12:01:44PM -0800, Daniele Ceraolo Spurio wrote:
> Explicitly using NULL is the correct approach.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202502050322.VUBMyUHc-lkp@intel.com/
> Fixes: dcdd6b84d9ac ("drm/xe/pxp: Allocate PXP execution resources")
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> ---
>  drivers/gpu/drm/xe/xe_pxp_submit.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_pxp_submit.c b/drivers/gpu/drm/xe/xe_pxp_submit.c
> index b50fe037c74b..d92ec0f515b0 100644
> --- a/drivers/gpu/drm/xe/xe_pxp_submit.c
> +++ b/drivers/gpu/drm/xe/xe_pxp_submit.c
> @@ -54,7 +54,7 @@ static int allocate_vcs_execution_resources(struct xe_pxp *pxp)
>  	 * Each termination is 16 DWORDS, so 4K is enough to contain a
>  	 * termination for each sessions.
>  	 */
> -	bo = xe_bo_create_pin_map(xe, tile, 0, SZ_4K, ttm_bo_type_kernel,
> +	bo = xe_bo_create_pin_map(xe, tile, NULL, SZ_4K, ttm_bo_type_kernel,
>  				  XE_BO_FLAG_SYSTEM | XE_BO_FLAG_PINNED | XE_BO_FLAG_GGTT);

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

>  	if (IS_ERR(bo)) {
>  		err = PTR_ERR(bo);
> -- 
> 2.43.0
> 

  reply	other threads:[~2025-02-04 22:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 20:01 [PATCH] drm/xe/pxp: Don't use 0 to indicate NULL Daniele Ceraolo Spurio
2025-02-04 22:52 ` Rodrigo Vivi [this message]
2025-02-05  0:17 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-05  0:17 ` ✓ CI.checkpatch: " Patchwork
2025-02-05  0:18 ` ✓ CI.KUnit: " Patchwork
2025-02-05  0:34 ` ✓ CI.Build: " Patchwork
2025-02-05  0:37 ` ✓ CI.Hooks: " Patchwork
2025-02-05  0:38 ` ✓ CI.checksparse: " Patchwork
2025-02-05  0:57 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-02-05  6:34 ` ✗ Xe.CI.Full: " 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=Z6KaRFxc3iV9JqlN@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=John.C.Harrison@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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.