All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: RE: [PATCH v2] drm/{i915, xe}/display: add core workaround query to display parent interface
Date: Mon, 03 Aug 2026 14:55:01 +0300	[thread overview]
Message-ID: <90df57bc7908d2f6adefc0b2cd8f19c562d0e6e3@intel.com> (raw)
In-Reply-To: <DS4PPFE901A304FB7CAB444AB9AF146CF3BE3D52@DS4PPFE901A304F.namprd11.prod.outlook.com>

On Mon, 03 Aug 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
> Should we maybe have a comment documenting when it is okay to use this, basically use this only if unavoidable and when
> Required info is available in only core driver to avoid it being misused in future.

Makes sense, v3 with some comments sent.

> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>

Thanks,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2026-08-03 11:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 16:25 [PATCH] drm/{i915, xe}/display: add core workaround query to display parent interface Jani Nikula
2026-07-28 16:54 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2026-07-28 17:02 ` ✓ CI.KUnit: success " Patchwork
2026-07-28 17:02 ` [PATCH v2] " Jani Nikula
2026-08-03  3:00   ` Kandpal, Suraj
2026-08-03 11:55     ` Jani Nikula [this message]
2026-07-28 17:50 ` ✗ CI.checkpatch: warning for drm/{i915, xe}/display: add core workaround query to display parent interface (rev2) Patchwork
2026-07-28 17:51 ` ✓ CI.KUnit: success " Patchwork
2026-07-28 18:27 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-28 18:37 ` ✓ i915.CI.BAT: " Patchwork
2026-07-28 22:17 ` ✗ i915.CI.Full: failure " Patchwork
2026-07-28 22:24 ` ✓ Xe.CI.FULL: success " 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=90df57bc7908d2f6adefc0b2cd8f19c562d0e6e3@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@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.