From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH 8/8] drm/xe/display: Call display probe from i915 code
Date: Fri, 02 Jun 2023 20:33:12 +0300 [thread overview]
Message-ID: <87bkhxdb1j.fsf@intel.com> (raw)
In-Reply-To: <20230601163523.GI6953@mdroper-desk1.amr.corp.intel.com>
On Thu, 01 Jun 2023, Matt Roper <matthew.d.roper@intel.com> wrote:
> On Thu, Jun 01, 2023 at 12:24:09PM +0300, Jani Nikula wrote:
>> On Wed, 31 May 2023, Matt Roper <matthew.d.roper@intel.com> wrote:
>> > FIXME: These changes should have been a fixup patch against
>> > "drm/xe/display: Implement display support" but that commit has itself
>> > been mis-squashed somewhere and no longer exists.
>>
>> It's been mis-squashed into "drm/i915/irq: split out hotplug irq
>> handling" which should only be a cherry-pick from upstream.
>
> Since Rodrigo is out at the moment, who's handling the periodic rebase
> of drm-xe-next until he gets back? We should make sure unsquashing this
> is on their radar for whenever the next rebase happens.
Lucas fixed this one.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-06-02 17:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 22:48 [Intel-xe] [PATCH 0/8] Utilize i915 display probing Matt Roper
2023-05-31 22:48 ` [Intel-xe] [PATCH 1/8] drm/i915/display: Move display device info to header under display/ Matt Roper
2023-05-31 22:48 ` [Intel-xe] [PATCH 2/8] drm/i915: Convert INTEL_INFO()->display to a pointer Matt Roper
2023-05-31 22:48 ` [Intel-xe] [PATCH 3/8] drm/i915/display: Move display runtime info to display structure Matt Roper
2023-05-31 22:48 ` [Intel-xe] [PATCH 4/8] drm/i915/display: Make display responsible for probing its own IP Matt Roper
2023-05-31 22:48 ` [Intel-xe] [PATCH 5/8] drm/i915/display: Handle GMD_ID identification in display code Matt Roper
2023-05-31 22:48 ` [Intel-xe] [PATCH 6/8] drm/i915/display: Move feature test macros to intel_display_device.h Matt Roper
2023-05-31 22:48 ` [Intel-xe] [PATCH 7/8] drm/i915/display: Include of display limits doesn't need 'display/' Matt Roper
2023-05-31 22:48 ` [Intel-xe] [PATCH 8/8] drm/xe/display: Call display probe from i915 code Matt Roper
2023-06-01 9:24 ` Jani Nikula
2023-06-01 16:35 ` Matt Roper
2023-06-02 17:33 ` Jani Nikula [this message]
2023-05-31 22:50 ` [Intel-xe] ✓ CI.Patch_applied: success for Utilize i915 display probing Patchwork
2023-05-31 22:52 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-31 22:56 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-31 23:26 ` [Intel-xe] ○ CI.BAT: info " Patchwork
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=87bkhxdb1j.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@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