From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
Ville Syrjala <ville.syrjala@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Subject: RE: [PATCH] drm/i915: Give i915 and xe each their own display tracepoints
Date: Tue, 28 Jan 2025 11:50:54 +0200 [thread overview]
Message-ID: <87ed0n9sht.fsf@intel.com> (raw)
In-Reply-To: <CH0PR11MB54445354D7CADC3046E2905EE5EC2@CH0PR11MB5444.namprd11.prod.outlook.com>
On Mon, 27 Jan 2025, "Cavitt, Jonathan" <jonathan.cavitt@intel.com> wrote:
> Though it would probably be good to file an issue report detailing
> the issue this fixes, then mark this patch as having fixed that
> reported issue.
While I occasionally do request that when we get patches out of left
field, and I want to ensure we have a full understanding of the problem,
please let's not add extra hurdles for ourselves for fixing stuff.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-01-28 9:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 21:30 [PATCH] drm/i915: Give i915 and xe each their own display tracepoints Ville Syrjala
2025-01-27 21:40 ` Cavitt, Jonathan
2025-01-28 9:50 ` Jani Nikula [this message]
2025-01-28 16:50 ` Ville Syrjälä
2025-01-27 22:22 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-27 22:22 ` ✓ CI.checkpatch: " Patchwork
2025-01-27 22:23 ` ✓ CI.KUnit: " Patchwork
2025-01-27 22:40 ` ✓ CI.Build: " Patchwork
2025-01-27 22:42 ` ✓ CI.Hooks: " Patchwork
2025-01-27 22:43 ` ✓ CI.checksparse: " Patchwork
2025-01-27 23:00 ` [PATCH] " Lucas De Marchi
2025-01-28 16:50 ` Ville Syrjälä
2025-01-27 23:04 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-01-28 11:55 ` ✗ Xe.CI.Full: 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=87ed0n9sht.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=ville.syrjala@linux.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