From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Jouni Högander" <jouni.hogander@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 3/4] fixup! drm/xe: Introduce a new DRM driver for Intel GPUs
Date: Wed, 20 Sep 2023 16:02:41 -0400 [thread overview]
Message-ID: <ZQtP4YvzBrK5osx/@intel.com> (raw)
In-Reply-To: <20230918070100.1387082-4-jouni.hogander@intel.com>
On Mon, Sep 18, 2023 at 10:00:59AM +0300, Jouni Högander wrote:
> intel_runtime_pm is ok for Xe driver as well. Especially as this
> whole struct is here just to kill some build problems.
I'm not sure if I like this. git grep intel_runtime_pm and you will
understand.
But also you made me thing now... we should probably simply remove
this line from this original patch. And then only introduce back
on the display patch.
And in anyway I'd prefer some define in the compat-headers,
rather then in here.
>
> Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/xe/xe_device_types.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_device_types.h b/drivers/gpu/drm/xe/xe_device_types.h
> index a82f28c6a3a0..ae18097cf8ea 100644
> --- a/drivers/gpu/drm/xe/xe_device_types.h
> +++ b/drivers/gpu/drm/xe/xe_device_types.h
> @@ -402,7 +402,7 @@ struct xe_device {
> u32 edram_size_mb;
>
> /* To shut up runtime pm macros.. */
> - struct xe_runtime_pm {} runtime_pm;
> + struct intel_runtime_pm {} runtime_pm;
>
> /* For pcode */
> struct mutex sb_lock;
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-09-20 20:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 7:00 [Intel-xe] [PATCH 0/4] Xe runtime pm refactoring Jouni Högander
2023-09-18 7:00 ` [Intel-xe] [PATCH 1/4] Revert "FIXME: drm/i915: runtime pm changes" Jouni Högander
2023-09-18 21:20 ` Govindapillai, Vinod
2023-09-18 7:00 ` [Intel-xe] [PATCH 2/4] drm/i915: Remove runtime suspended boolean from intel_runtime_pm struct Jouni Högander
2023-09-18 21:21 ` Govindapillai, Vinod
2023-09-18 7:00 ` [Intel-xe] [PATCH 3/4] fixup! drm/xe: Introduce a new DRM driver for Intel GPUs Jouni Högander
2023-09-18 21:22 ` Govindapillai, Vinod
2023-09-20 20:02 ` Rodrigo Vivi [this message]
2023-09-21 11:15 ` Hogander, Jouni
2023-09-18 7:01 ` [Intel-xe] [PATCH 4/4] fixup! drm/xe/display: Implement display support Jouni Högander
2023-09-18 21:22 ` Govindapillai, Vinod
2023-09-18 7:27 ` [Intel-xe] ✓ CI.Patch_applied: success for Xe runtime pm refactoring Patchwork
2023-09-18 7:28 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-18 7:29 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-18 7:36 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-18 7:36 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-09-18 7:38 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-18 8:10 ` [Intel-xe] ✓ CI.BAT: success " 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=ZQtP4YvzBrK5osx/@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jouni.hogander@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