All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	"Michał Grzelak" <michal.grzelak@intel.com>
Subject: Re: [RESEND 0/4] drm/i915/display: start switching to display specific reg types
Date: Wed, 13 May 2026 16:50:11 +0300	[thread overview]
Message-ID: <558ac9d46f77130a5a70cd16c6e7af65717682a1@intel.com> (raw)
In-Reply-To: <agRvJsmqqi1q0MnL@intel.com>

On Wed, 13 May 2026, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Fri, May 08, 2026 at 02:29:50PM +0300, Jani Nikula wrote:
>> 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?
>
> Looks fine by me
>
> For the series
> Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Thanks for the review and ack, pushed to drm-intel-next.

BR,
Jani.


-- 
Jani Nikula, Intel

      reply	other threads:[~2026-05-13 13:50 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 ` [RESEND 0/4] drm/i915/display: start switching to display specific reg types Jani Nikula
2026-05-13 12:31   ` Ville Syrjälä
2026-05-13 13:50     ` 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=558ac9d46f77130a5a70cd16c6e7af65717682a1@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.