All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2 2/2] oa/i915: Add ARL standlone oa files
Date: Mon, 04 Nov 2024 13:06:21 -0800	[thread overview]
Message-ID: <85ses6yaia.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20241104205201.175541-2-jose.souza@intel.com>

On Mon, 04 Nov 2024 12:52:00 -0800, José Roberto de Souza wrote:
>

Hi Jose,

> There is suficient differences between generated ARL OA files and
> MTL ones for us to generated and split ARL to its own files.
>
> v2:
> - add missing arl check in perf-metricset-codegen.py

These work this time correct, unlike the last time where something was
wrong? Maybe it was due to this?

The subject should be lib/i915/perf (which Kamil requested the last time),
but I can fix that up before merging. Unless you can merge, in that case
please fix this up.

Otherwise:

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

>
> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>


  reply	other threads:[~2024-11-04 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 20:51 [PATCH i-g-t v2 1/2] i915/perf: Fix invalid escape warnings José Roberto de Souza
2024-11-04 20:52 ` [PATCH i-g-t v2 2/2] oa/i915: Add ARL standlone oa files José Roberto de Souza
2024-11-04 21:06   ` Dixit, Ashutosh [this message]
2024-11-04 21:10     ` Souza, Jose
2024-11-05 14:29       ` Souza, Jose
2024-11-04 20:56 ` [PATCH i-g-t v2 1/2] i915/perf: Fix invalid escape warnings Dixit, Ashutosh
2024-11-05 10:56 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,v2,1/2] " Patchwork
2024-11-05 11:29 ` ✓ CI.xeBAT: " Patchwork
2024-11-06 12:53 ` ✗ CI.xeFULL: 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=85ses6yaia.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jose.souza@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 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.