Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Brost, Matthew" <matthew.brost@intel.com>
Subject: RE: [PATCH] drm/xe/compat: Remove unused i915_reg.h from compat header
Date: Thu, 26 Feb 2026 11:42:37 +0200	[thread overview]
Message-ID: <5c2d7382a694a16ce272543ae8812a6429b33928@intel.com> (raw)
In-Reply-To: <DM4PR11MB63609181C06EA2208BD6B33CF472A@DM4PR11MB6360.namprd11.prod.outlook.com>

On Thu, 26 Feb 2026, "Shankar, Uma" <uma.shankar@intel.com> wrote:
> Thanks Jani, shall I send a revert on drm-xe-next and push through
> drm-intel-next instead ?

Yes, please.

> Apologies for the noise on this.

No worries, it happens.

BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2026-02-26  9:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 17:10 [PATCH] drm/xe/compat: Remove unused i915_reg.h from compat header Uma Shankar
2026-02-23 16:59 ` ✗ CI.checkpatch: warning for " Patchwork
2026-02-23 17:01 ` ✓ CI.KUnit: success " Patchwork
2026-02-24 13:07 ` [PATCH] " Jani Nikula
2026-02-24 13:25   ` Shankar, Uma
2026-02-25 16:40   ` Shankar, Uma
2026-02-25 17:43     ` Matt Roper
2026-02-25 18:11       ` Jani Nikula
2026-02-26  6:54         ` Shankar, Uma
2026-02-26  9:42           ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-26 17:55 Uma Shankar
2026-02-27  6:47 ` Shankar, Uma

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=5c2d7382a694a16ce272543ae8812a6429b33928@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=uma.shankar@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