From: Jani Nikula <jani.nikula@intel.com>
To: Luca Coelho <luca@coelho.fi>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 0/8] drm/i915/sbi: move under display, cleanup
Date: Wed, 04 Jun 2025 16:41:15 +0300 [thread overview]
Message-ID: <a94b4b15c6f29b2d2ae92792752201facddbc212@intel.com> (raw)
In-Reply-To: <cfbc556cc87c30ce5b122dd95f81e73327a5e3cb.camel@coelho.fi>
On Wed, 04 Jun 2025, Luca Coelho <luca@coelho.fi> wrote:
> On Tue, 2025-05-13 at 15:16 +0300, Jani Nikula wrote:
>> Move SBI under display, and convert to display structures and
>> interfaces.
>>
>> TODO: Also find places for sbi init/fini within display.
>>
>> BR,
>> Jani.
>
> Very straightforward, clean patches. Easy to review, kudos!
>
> Reviewed-by: Luca Coelho <luciano.coelho@intel.com>
Many thanks, pushed to drm-intel-next. Well, actually pushed the rebased
patches [1], there are no meaningful differences, I think just a couple
of conflicts in #include lists.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1748343520.git.jani.nikula@intel.com
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-06-04 13:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 12:16 [PATCH 0/8] drm/i915/sbi: move under display, cleanup Jani Nikula
2025-05-13 12:17 ` [PATCH 1/8] drm/i915/sbi: move intel_sbi.[ch] under display/ Jani Nikula
2025-05-13 12:17 ` [PATCH 2/8] drm/i915/sbi: convert intel_sbi.[ch] to struct intel_display Jani Nikula
2025-05-13 12:17 ` [PATCH 3/8] drm/i915/sbi: move sbi_lock under " Jani Nikula
2025-05-13 12:17 ` [PATCH 4/8] drm/i915/de: rename timeout parameters timeout_ms to highlight unit Jani Nikula
2025-05-13 12:17 ` [PATCH 5/8] drm/i915: add out_value to intel_wait_for_register_fw() and intel_de_wait_fw() Jani Nikula
2025-05-13 12:17 ` [PATCH 6/8] drm/i915/sbi: convert to intel_de_*() Jani Nikula
2025-05-13 12:17 ` [PATCH 7/8] drm/i915/sbi: split out intel_sbi_regs.h Jani Nikula
2025-05-13 12:17 ` [PATCH 8/8] drm/i915/sbi: clean up SBI register macro definitions and usage Jani Nikula
2025-05-14 10:37 ` ✓ CI.Patch_applied: success for drm/i915/sbi: move under display, cleanup Patchwork
2025-05-14 10:37 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-14 10:38 ` ✓ CI.KUnit: success " Patchwork
2025-05-14 10:49 ` ✓ CI.Build: " Patchwork
2025-05-14 10:51 ` ✓ CI.Hooks: " Patchwork
2025-05-14 10:53 ` ✗ CI.checksparse: warning " Patchwork
2025-05-14 11:17 ` ✓ Xe.CI.BAT: success " Patchwork
2025-05-14 14:51 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-26 23:33 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-26 23:33 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-26 23:34 ` ✓ CI.KUnit: success " Patchwork
2025-05-26 23:45 ` ✓ CI.Build: " Patchwork
2025-06-04 12:34 ` [PATCH 0/8] " Luca Coelho
2025-06-04 13:41 ` 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=a94b4b15c6f29b2d2ae92792752201facddbc212@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=luca@coelho.fi \
/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