From: Jani Nikula <jani.nikula@intel.com>
To: "Grzelak, Michal" <michal.grzelak@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 0/2] drm/i915/display: register include cleanups
Date: Wed, 11 Jun 2025 14:08:41 +0300 [thread overview]
Message-ID: <8c245e4c64305d4c884f20bd61bd6a3914194428@intel.com> (raw)
In-Reply-To: <PH0PR11MB5062EED5AC7326D84984EEBF8F6AA@PH0PR11MB5062.namprd11.prod.outlook.com>
On Tue, 10 Jun 2025, "Grzelak, Michal" <michal.grzelak@intel.com> wrote:
> Looks good to me, for the whole series:
> Reviewed-by: Michał Grzelak <michal.grzelak@intel.com>
Thanks for the review, pushed to drm-intel-next.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-06-11 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 11:53 [PATCH 0/2] drm/i915/display: register include cleanups Jani Nikula
2025-06-09 11:53 ` [PATCH 1/2] drm/i915/display: include intel_display_reg_defs.h from display regs files Jani Nikula
2025-06-09 11:53 ` [PATCH 2/2] drm/i915/display: drop i915_reg.h include where possible Jani Nikula
2025-06-09 16:14 ` ✓ CI.Patch_applied: success for drm/i915/display: register include cleanups Patchwork
2025-06-09 16:14 ` ✓ CI.checkpatch: " Patchwork
2025-06-09 16:16 ` ✓ CI.KUnit: " Patchwork
2025-06-09 16:26 ` ✓ CI.Build: " Patchwork
2025-06-09 16:29 ` ✓ CI.Hooks: " Patchwork
2025-06-09 16:31 ` ✗ CI.checksparse: warning " Patchwork
2025-06-09 17:07 ` ✓ Xe.CI.BAT: success " Patchwork
2025-06-09 18:21 ` ✗ Xe.CI.Full: failure " Patchwork
2025-06-10 18:00 ` [PATCH 0/2] " Grzelak, Michal
2025-06-11 11:08 ` Jani Nikula [this message]
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=8c245e4c64305d4c884f20bd61bd6a3914194428@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.grzelak@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