All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [Intel-xe] [PATCH 2/2] fixup! drm/i915/display: Remaining changes to make xe compile
Date: Thu, 11 May 2023 15:32:10 +0300	[thread overview]
Message-ID: <87pm77kq0l.fsf@intel.com> (raw)
In-Reply-To: <ui4rcyti66dcl3qtxpt4qmqz4xfwsczi6ym4svtlyfhh5idlh6@eicqy7iuk4sc>

On Wed, 10 May 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Wed, May 10, 2023 at 06:46:44PM +0300, Jani Nikula wrote:
>>Currently "drm/xe: Introduce a new DRM driver for Intel GPUs" removes
>>these lines, so don't add them in "drm/i915/display: Remaining changes
>>to make xe compile" to begin with!
>>
>>Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>---
>> drivers/gpu/drm/i915/i915_reg_defs.h | 4 ----
>> 1 file changed, 4 deletions(-)
>>
>>diff --git a/drivers/gpu/drm/i915/i915_reg_defs.h b/drivers/gpu/drm/i915/i915_reg_defs.h
>>index a7c4101370ad..eac5a4141bfa 100644
>>--- a/drivers/gpu/drm/i915/i915_reg_defs.h
>>+++ b/drivers/gpu/drm/i915/i915_reg_defs.h
>>@@ -218,13 +218,9 @@ typedef struct {
>>
>> #define _MMIO(r) ((const i915_reg_t){ .reg = (r) })
>>
>>-#ifdef I915
>> typedef struct {
>> 	u32 reg;
>> } i915_mcr_reg_t;
>>-#else
>>-#define i915_mcr_reg_t i915_reg_t
>>-#endif
>
>
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>

Thanks, pushed to drm-xe-next.

BR,
Jani.

>
> Lucas De Marchi
>
>>
>> #define MCR_REG(offset)	((const i915_mcr_reg_t){ .reg = (offset) })
>>
>>-- 
>>2.39.2
>>

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-05-11 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 15:46 [Intel-xe] [PATCH 1/2] DUMMY COMMIT. REMOVE AT NEXT REBASE Jani Nikula
2023-05-10 15:46 ` [Intel-xe] [PATCH 2/2] fixup! drm/i915/display: Remaining changes to make xe compile Jani Nikula
2023-05-10 20:29   ` Lucas De Marchi
2023-05-11 12:32     ` Jani Nikula [this message]
2023-05-10 15:53 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2] DUMMY COMMIT. REMOVE AT NEXT REBASE Patchwork
2023-05-10 15:54 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-10 15:58 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-10 16:28 ` [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=87pm77kq0l.fsf@intel.com \
    --to=jani.nikula@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 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.