Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Sai Teja Pottumuttu <sai.teja.pottumuttu@intel.com>
Cc: <igt-dev@lists.freedesktop.org>,
	<umesh.nerlige.ramappa@intel.com>, <matthew.d.roper@intel.com>,
	<zbigniew.kempczynski@intel.com>
Subject: Re: [PATCH i-g-t] lib/intel_batchbuffer: Refactor igt_get_render_copyfunc
Date: Mon, 24 Mar 2025 21:33:24 -0700	[thread overview]
Message-ID: <87h63hafvv.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250324093627.3711195-1-sai.teja.pottumuttu@intel.com>

On Mon, 24 Mar 2025 02:36:27 -0700, Sai Teja Pottumuttu wrote:
>
> +++ b/lib/intel_batchbuffer.c
> @@ -652,9 +652,15 @@ void igt_blitter_fast_copy__raw(int fd,
>   * specified with @devid. Will return NULL when no render copy function is
>   * implemented.
>   */
> -igt_render_copyfunc_t igt_get_render_copyfunc(int devid)
> +igt_render_copyfunc_t igt_get_render_copyfunc(int fd)
>  {
>	igt_render_copyfunc_t copy = NULL;
> +	int devid;
> +
> +	if(is_xe_device(fd) && !xe_has_engine_class(fd, DRM_XE_ENGINE_CLASS_RENDER))

Needs a space after if. I can change that when merging, no need to
resend. Otherwise LGTM:

Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>

But let's see if anyone else has any comments.

Thanks.
--
Ashutosh

  parent reply	other threads:[~2025-03-25  4:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24  9:36 [PATCH i-g-t] lib/intel_batchbuffer: Refactor igt_get_render_copyfunc Sai Teja Pottumuttu
2025-03-24 22:22 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-03-24 22:37 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-25  2:11 ` ✗ Xe.CI.Full: " Patchwork
2025-03-25  4:33 ` Dixit, Ashutosh [this message]
2025-03-25 18:48   ` [PATCH i-g-t] " Dixit, Ashutosh

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=87h63hafvv.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=sai.teja.pottumuttu@intel.com \
    --cc=umesh.nerlige.ramappa@intel.com \
    --cc=zbigniew.kempczynski@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