From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Michał Grzelak" <michal.grzelak@intel.com>,
ville.syrjala@linux.intel.com
Subject: Re: [RESEND 0/4] drm/i915/display: start switching to display specific reg types
Date: Fri, 08 May 2026 14:29:50 +0300 [thread overview]
Message-ID: <0fb8d06a63af7f22dea6d08d69d94350c97a1e83@intel.com> (raw)
In-Reply-To: <cover.1777972548.git.jani.nikula@intel.com>
On Tue, 05 May 2026, Jani Nikula <jani.nikula@intel.com> wrote:
> Jani Nikula (4):
> drm/i915/display: add typedef for intel_reg_t and use it
> drm/i915/display: add struct intel_irq_regs and use it
> drm/i915/display: add struct intel_error_regs and use it
> drm/i915/display: define and use intel_reg_{offset,equal,valid}()
> helpers
Ville, ack on this one?
BR,
Jani
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-05-08 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 9:16 [RESEND 0/4] drm/i915/display: start switching to display specific reg types Jani Nikula
2026-05-05 9:16 ` [RESEND 1/4] drm/i915/display: add typedef for intel_reg_t and use it Jani Nikula
2026-05-05 9:16 ` [RESEND 2/4] drm/i915/display: add struct intel_irq_regs " Jani Nikula
2026-05-05 9:16 ` [RESEND 3/4] drm/i915/display: add struct intel_error_regs " Jani Nikula
2026-05-05 9:16 ` [RESEND 4/4] drm/i915/display: define and use intel_reg_{offset, equal, valid}() helpers Jani Nikula
2026-05-05 9:36 ` ✗ CI.checkpatch: warning for drm/i915/display: start switching to display specific reg types (rev2) Patchwork
2026-05-05 9:37 ` ✓ CI.KUnit: success " Patchwork
2026-05-05 11:00 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-05 13:13 ` ✓ i915.CI.BAT: " Patchwork
2026-05-05 19:41 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-05 21:11 ` ✗ i915.CI.Full: " Patchwork
2026-05-08 11:29 ` Jani Nikula [this message]
2026-05-13 12:31 ` [RESEND 0/4] drm/i915/display: start switching to display specific reg types Ville Syrjälä
2026-05-13 13:50 ` Jani Nikula
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=0fb8d06a63af7f22dea6d08d69d94350c97a1e83@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.grzelak@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 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.