From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: remove stale runtime_pm member
Date: Thu, 13 Nov 2025 10:40:49 +0200 [thread overview]
Message-ID: <20777272c8c439d25e1ecf92669f621f6074fee4@intel.com> (raw)
In-Reply-To: <aRTh7OPupcEh1qW2@intel.com>
On Wed, 12 Nov 2025, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Wed, Nov 12, 2025 at 08:55:47PM +0200, Jani Nikula wrote:
>> This has become unused and unnecessary. Remove.
>
> \o/
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> (trusting more your compiler than my eyes)
Thanks, pushed via drm-intel-next as there's more to come in this area.
BR,
Jani.
>
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_device_types.h | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_device_types.h b/drivers/gpu/drm/xe/xe_device_types.h
>> index 7baf15f51575..0b2fa7c56d38 100644
>> --- a/drivers/gpu/drm/xe/xe_device_types.h
>> +++ b/drivers/gpu/drm/xe/xe_device_types.h
>> @@ -656,9 +656,6 @@ struct xe_device {
>> */
>> u32 edram_size_mb;
>>
>> - /* To shut up runtime pm macros.. */
>> - struct xe_runtime_pm {} runtime_pm;
>> -
>> struct intel_uncore {
>> spinlock_t lock;
>> } uncore;
>> --
>> 2.47.3
>>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-11-13 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 18:55 [PATCH] drm/xe: remove stale runtime_pm member Jani Nikula
2025-11-12 19:37 ` Rodrigo Vivi
2025-11-13 8:40 ` Jani Nikula [this message]
2025-11-12 23:30 ` ✓ i915.CI.BAT: success for " Patchwork
2025-11-13 3:03 ` ✓ i915.CI.Full: " 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=20777272c8c439d25e1ecf92669f621f6074fee4@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).