Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Anusha Srivatsa <anusha.srivatsa@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/5] fixup! drm/xe/rplu: s/ADLP/ALDERLAKE_P
Date: Fri, 06 Oct 2023 10:39:52 +0300	[thread overview]
Message-ID: <87ttr46vxz.fsf@intel.com> (raw)
In-Reply-To: <ZR8DWVeXtkrIU8Uj@intel.com>

On Thu, 05 Oct 2023, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Wed, Oct 04, 2023 at 01:16:48PM -0500, Lucas De Marchi wrote:
>> On Wed, Oct 04, 2023 at 10:58:05AM +0300, Jani Nikula wrote:
>> > On Tue, 03 Oct 2023, Anusha Srivatsa <anusha.srivatsa@intel.com> wrote:
>> > > Extend the change introduced in the previous patch to xe
>> > > driver.
>> > 
>> > This is not a fixup to the previous patch. This needs to be a fixup to
>> > the commit that added the file to begin with.
>> > 
>> > The order of the patches will be changed to add display enabling last.
>> 
>> 
>> assuming we are still going to move display up. Rodrigo mentioned
>> recently about maybe stopping that. +Rodrigo
>
> I hope we don't need to move them up anymore. but let's revisit this
> in about 2 weeks.

I don't think that's the right choice. Please don't lock xe core and
display upstreaming together, even if everyone wants them to happen
together.

This ambiguous approach means we don't know whether to use fixups or
regular commits.

BR,
Jani.



>
>> 
>> In this case the commit message should be:
>> 
>> 	Subject: fixup! drm/xe/display: Implement display support
>
> since this is the fixup, then the right placement is as first patch
> in the series to avoid further conflicts when autosquashing without
> moving the rest of display up.
>
>> 
>> Lucas De Marchi
>> 
>> > 
>> > BR,
>> > Jani.
>> > 
>> > > 
>> > > Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
>> > > ---
>> > >  drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h | 2 +-
>> > >  1 file changed, 1 insertion(+), 1 deletion(-)
>> > > 
>> > > diff --git a/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h b/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h
>> > > index 7c825f129166..918dd27868fa 100644
>> > > --- a/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h
>> > > +++ b/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h
>> > > @@ -146,7 +146,7 @@ static inline struct drm_i915_private *kdev_to_i915(struct device *kdev)
>> > >  #define IS_DG2_G10(xe) ((xe)->info.subplatform == XE_SUBPLATFORM_DG2_G10)
>> > >  #define IS_DG2_G11(xe) ((xe)->info.subplatform == XE_SUBPLATFORM_DG2_G11)
>> > >  #define IS_DG2_G12(xe) ((xe)->info.subplatform == XE_SUBPLATFORM_DG2_G12)
>> > > -#define IS_RAPTORLAKE_U(xe) ((xe)->info.subplatform == XE_SUBPLATFORM_ADLP_RPLU)
>> > > +#define IS_RAPTORLAKE_U(xe) ((xe)->info.subplatform == XE_SUBPLATFORM_ALDERLAKE_P_RPLU)
>> > >  #define IS_ICL_WITH_PORT_F(xe) (xe && 0)
>> > >  #define HAS_FLAT_CCS(xe) (xe_device_has_flat_ccs(xe))
>> > >  #define to_intel_bo(x) gem_to_xe_bo((x))
>> > 
>> > -- 
>> > Jani Nikula, Intel

-- 
Jani Nikula, Intel

  reply	other threads:[~2023-10-06  7:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 20:37 [Intel-xe] [PATCH 0/5] Add Raptorlake Support Anusha Srivatsa
2023-10-03 20:37 ` [Intel-xe] [PATCH 1/5] drm/xe/rplu: s/ADLP/ALDERLAKE_P Anusha Srivatsa
2023-10-04 18:12   ` Lucas De Marchi
2023-10-03 20:37 ` [Intel-xe] [PATCH 2/5] fixup! " Anusha Srivatsa
2023-10-04  7:58   ` Jani Nikula
2023-10-04 18:16     ` Lucas De Marchi
2023-10-05 18:41       ` Rodrigo Vivi
2023-10-06  7:39         ` Jani Nikula [this message]
2023-10-03 20:37 ` [Intel-xe] [PATCH 3/5] drm/xe/rpls: Add RPLS Support Anusha Srivatsa
2023-10-04 18:19   ` Lucas De Marchi
2023-10-03 20:37 ` [Intel-xe] [PATCH 4/5] drm/xe/rpls: Add Stepping info for RPLS Anusha Srivatsa
2023-10-04 18:20   ` Lucas De Marchi
2023-10-03 20:37 ` [Intel-xe] [PATCH 5/5] drm/xe: Add missing ADL entries to xe_test_wa Anusha Srivatsa
2023-10-04 18:20   ` Lucas De Marchi
2023-10-03 22:04 ` [Intel-xe] ✓ CI.Patch_applied: success for Add Raptorlake Support (rev3) Patchwork
2023-10-03 22:04 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-10-03 22:06 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-10-03 22:13 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-03 22:13 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-10-03 22:14 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-10-03 22:52 ` [Intel-xe] ✓ CI.BAT: " 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=87ttr46vxz.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=anusha.srivatsa@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@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