Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Roper, Matthew D" <matthew.d.roper@intel.com>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: RE: [PATCH] Revert "drm/xe/display: use xe->display to decide whether to do anything"
Date: Wed, 11 Jun 2025 14:02:28 +0300	[thread overview]
Message-ID: <5f874ab8a2469bfd08addeb441e98e4462b67111@intel.com> (raw)
In-Reply-To: <IA0PR11MB718568265F56A8EC2FC009B1F875A@IA0PR11MB7185.namprd11.prod.outlook.com>

On Wed, 11 Jun 2025, "Kasireddy, Vivek" <vivek.kasireddy@intel.com> wrote:
> I do not have commit access to drm-intel-next. So, I guess either you
> or Matt would need to merge it.

Pushed to drm-intel-next, thanks for the patch.

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2025-06-11 11:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05  5:42 [PATCH] Revert "drm/xe/display: use xe->display to decide whether to do anything" Vivek Kasireddy
2025-06-05  7:27 ` ✓ CI.Patch_applied: success for " Patchwork
2025-06-05  7:27 ` ✓ CI.checkpatch: " Patchwork
2025-06-05  7:29 ` ✓ CI.KUnit: " Patchwork
2025-06-05  7:42 ` ✓ CI.Build: " Patchwork
2025-06-05  7:45 ` ✓ CI.Hooks: " Patchwork
2025-06-05  7:46 ` ✓ CI.checksparse: " Patchwork
2025-06-05  7:55 ` [PATCH] " Jani Nikula
2025-06-10  7:56   ` Jani Nikula
2025-06-11  5:03     ` Kasireddy, Vivek
2025-06-11 11:02       ` Jani Nikula [this message]
2025-06-05  9:03 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-06-06 18:19 ` ✗ 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=5f874ab8a2469bfd08addeb441e98e4462b67111@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=vivek.kasireddy@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