Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: priyanka.dandamudi@intel.com
Cc: igt-dev@lists.freedesktop.org, saurabhg.gupta@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] lib/igt_gt: Check for shared reset domain
Date: Fri, 07 Jan 2022 12:26:30 -0800	[thread overview]
Message-ID: <87mtk7gumh.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20220107161920.1643369-2-priyanka.dandamudi@intel.com>

On Fri, 07 Jan 2022 08:19:19 -0800, <priyanka.dandamudi@intel.com> wrote:
>
> +bool has_shared_reset_domain(int fd, const intel_ctx_t *ctx, const struct intel_execution_engine2 *e)

e is just a variable for the iterator, do not pass it in, declare locally.

> +	for_each_ctx_engine (fd, ctx, e) {
> +                if (rcs0 && ccs0)
> +                        break;
> +                else if (e->class == I915_ENGINE_CLASS_RENDER && e->instance == 0)
> +                                rcs0 = true;
> +                else if (e->class == I915_ENGINE_CLASS_COMPUTE && e->instance == 0)
> +                                ccs0 = true;
> +        }
> +        return (rcs0 && ccs0);

* Code above uses spaces instead of tabs
* Indentation is wrong
* Check for e->instance is unnecessary, remove it

Let's fix this cosmetic stuff first and then we can actually review the
patch and see how it gels with other series pending review in this area.

  reply	other threads:[~2022-01-07 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 16:19 [igt-dev] [PATCH i-g-t 0/2] Shared reset domain priyanka.dandamudi
2022-01-07 16:19 ` [igt-dev] [PATCH i-g-t 1/2] lib/igt_gt: Check for shared " priyanka.dandamudi
2022-01-07 20:26   ` Dixit, Ashutosh [this message]
2022-01-07 16:19 ` [igt-dev] [PATCH i-g-t 2/2] tests/i915/gem_ctx_exec: Skip test " priyanka.dandamudi
2022-01-07 17:54 ` [igt-dev] ✓ Fi.CI.BAT: success for Shared " Patchwork
2022-01-07 20:49 ` [igt-dev] ✓ Fi.CI.IGT: " 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=87mtk7gumh.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=priyanka.dandamudi@intel.com \
    --cc=saurabhg.gupta@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