From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [Intel-xe] [PATCH 0/1] Synchronize ext/intel_dram.c with the i915 source
Date: Wed, 05 Jul 2023 13:13:11 +0300 [thread overview]
Message-ID: <87ttuizmx4.fsf@intel.com> (raw)
In-Reply-To: <20230704160907.2173428-1-lucas.demarchi@intel.com>
On Tue, 04 Jul 2023, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> We can probably ifdef out most of intel_dram.c and stop copying it to
> ext/intel_dram.c, but there some abstractions that would be needed for
> e.g. the intel_uncore vs intel_de. Kick that can down the road and just
> do the needed change for MTL.
As it happens, I just did all that with [1].
Lucas already reviewed it (thanks!), this mail is for the benefit of
everyone else.
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/120181/
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2023-07-05 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 16:09 [Intel-xe] [PATCH 0/1] Synchronize ext/intel_dram.c with the i915 source Lucas De Marchi
2023-07-04 16:09 ` [Intel-xe] [PATCH 1/1] fixup! drm/xe/display: Implement display support Lucas De Marchi
2023-07-04 18:22 ` [Intel-xe] ✓ CI.Patch_applied: success for Synchronize ext/intel_dram.c with the i915 source Patchwork
2023-07-04 18:23 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-07-04 18:24 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-07-04 18:28 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-04 18:28 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-04 18:29 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-04 19:14 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-07-05 10:13 ` 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=87ttuizmx4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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.