From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Shekhar Chauhan <shekhar.chauhan@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH] tools/xe-perf-recorder: expose some OA stream open properties
Date: Wed, 29 Jul 2026 19:46:56 -0700 [thread overview]
Message-ID: <87a4r9gpnj.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <715ff9f8-217c-4ac6-818d-e79aaa4a4758@intel.com>
On Mon, 27 Jul 2026 23:40:50 -0700, Shekhar Chauhan wrote:
>
> Couple of things to note:
>
> On 7/28/2026 12:06, Shekhar Chauhan wrote:
> > xe-perf-recorder only passes 5 of the OA stream open properties to
> > DRM_XE_OBSERVATION_OP_STREAM_OPEN, leaving the rest without an open
> > source consumer. Add few of the remaining ones.
> 1. I missed out on adding "PATCH i-g-t" prefix, I did send it with a
> subject-prefix="PATCH i-g-t" hoping it'll append that, but turns out, it
> didn't, so I think I should explicitly do that while doing a git
> format-patch. I remember being told to add it in the gitconfig, but, I
> didn't wanna do it for all the patches that I send, so I didn't add there.
No, this is is what I said:
This can be configured in your .git/config:
[format]
subjectprefix = PATCH i-g-t
So this .git/config in your IGT repo, not your global ~/.gitconfig.
next prev parent reply other threads:[~2026-07-30 2:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 6:36 [PATCH] tools/xe-perf-recorder: expose some OA stream open properties Shekhar Chauhan
2026-07-28 6:40 ` Shekhar Chauhan
2026-07-30 2:46 ` Dixit, Ashutosh [this message]
2026-07-28 7:56 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-07-28 8:02 ` ✓ i915.CI.BAT: " Patchwork
2026-07-28 10:39 ` ✗ i915.CI.Full: failure " Patchwork
2026-07-28 11:08 ` ✗ Xe.CI.FULL: " Patchwork
2026-07-30 2:54 ` [PATCH] " Dixit, Ashutosh
2026-07-30 8:13 ` Shekhar Chauhan
2026-07-30 16:20 ` 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=87a4r9gpnj.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=shekhar.chauhan@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