From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@kernel.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe@lists.freedesktop.org, "Vivi,
Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH 1/2] fixup! drm/i915/display: Remaining changes to make xe compile
Date: Mon, 15 May 2023 19:42:48 +0300 [thread overview]
Message-ID: <87h6sdim0n.fsf@intel.com> (raw)
In-Reply-To: <ZGJEmhlyTFNcdUoR@rdvivi-mobl4>
On Mon, 15 May 2023, Rodrigo Vivi <rodrigo.vivi@kernel.org> wrote:
> On Mon, May 15, 2023 at 05:00:17PM +0300, Jani Nikula wrote:
>>
>> Lucas, Rodrigo, r-b on these two?
>
> I feel the order in the series is the opposite, but anyway,
> on the next clean up that will be fixed so, let's move with this
It's true, but would cause unnecessary conflicts every step of the
way. This doesn't.
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Thanks, pushed both to drm-xe-next.
BR,
Jani.
>
>>
>> Thanks,
>> Jani.
>>
>>
>> On Fri, 12 May 2023, Jani Nikula <jani.nikula@intel.com> wrote:
>> > The dependency on display/intel_display_reg_defs.h is removed by
>> > upstream commit 6e4e9fbd5ba0 ("drm/i915/gt: drop dependency on
>> > VLV_DISPLAY_BASE").
>> >
>> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> > ---
>> > drivers/gpu/drm/i915/gt/intel_gt_regs.h | 2 --
>> > 1 file changed, 2 deletions(-)
>> >
>> > diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> > index 7ae5fa5a8ff7..af80d2fe739b 100644
>> > --- a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> > +++ b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> > @@ -7,9 +7,7 @@
>> > #define __INTEL_GT_REGS__
>> >
>> > #include "i915_reg_defs.h"
>> > -#ifdef I915
>> > #include "display/intel_display_reg_defs.h" /* VLV_DISPLAY_BASE */
>> > -#endif
>> >
>> > /*
>> > * The perf control registers are technically multicast registers, but the
>>
>> --
>> Jani Nikula, Intel Open Source Graphics Center
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-05-15 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 7:43 [Intel-xe] [PATCH 1/2] fixup! drm/i915/display: Remaining changes to make xe compile Jani Nikula
2023-05-12 7:43 ` [Intel-xe] [PATCH 2/2] drm/i915/gt: drop dependency on VLV_DISPLAY_BASE Jani Nikula
2023-05-12 10:57 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] fixup! drm/i915/display: Remaining changes to make xe compile Patchwork
2023-05-12 10:59 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-12 11:03 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-12 11:24 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-05-15 14:00 ` [Intel-xe] [PATCH 1/2] " Jani Nikula
2023-05-15 14:41 ` Rodrigo Vivi
2023-05-15 16:42 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-31 15:18 [Intel-xe] [PATCH 0/2] drm/xe: Small cleanups to DPT code Maarten Lankhorst
2023-05-31 15:18 ` [Intel-xe] [PATCH 1/2] fixup! drm/i915/display: Remaining changes to make xe compile Maarten Lankhorst
2023-06-01 9:13 ` Jani Nikula
2023-08-14 8:37 Maarten Lankhorst
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=87h6sdim0n.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=rodrigo.vivi@kernel.org \
/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