From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: remove unused DISPLAY_PLANE_FLIP_PENDING() macro
Date: Thu, 26 Jun 2025 11:55:30 +0300 [thread overview]
Message-ID: <0b07ffe2091ebd0e26126237a544a0929ca36072@intel.com> (raw)
In-Reply-To: <aFv_q12bJXVF5GaR@intel.com>
On Wed, 25 Jun 2025, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Wed, Jun 25, 2025 at 04:21:40PM +0300, Jani Nikula wrote:
>> DISPLAY_PLANE_FLIP_PENDING() has been unused since commit fd3a40242e87
>> ("drm/i915: Rip out legacy page_flip completion/irq handling"). Remove.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Thanks, pushed to din, exceptionally without CI results because this is
certain not to cause regressions, and the build bot responded with
success.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/i915_reg.h | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>> index 04fb40867cc0..8d56b3c45451 100644
>> --- a/drivers/gpu/drm/i915/i915_reg.h
>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>> @@ -385,7 +385,6 @@
>> #define VLV_PCBR _MMIO(VLV_DISPLAY_BASE + 0x2120)
>> #define VLV_PCBR_ADDR_SHIFT 12
>>
>> -#define DISPLAY_PLANE_FLIP_PENDING(plane) (1 << (11 - (plane))) /* A and B only */
>> #define EIR _MMIO(0x20b0)
>> #define EMR _MMIO(0x20b4)
>> #define ESR _MMIO(0x20b8)
>> --
>> 2.39.5
>>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-06-26 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 13:21 [PATCH] drm/i915: remove unused DISPLAY_PLANE_FLIP_PENDING() macro Jani Nikula
2025-06-25 13:54 ` Rodrigo Vivi
2025-06-26 8:55 ` Jani Nikula [this message]
2025-06-25 14:27 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-06-25 18:44 ` ✗ i915.CI.BAT: failure for drm/i915: remove unused DISPLAY_PLANE_FLIP_PENDING() macro (rev2) 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=0b07ffe2091ebd0e26126237a544a0929ca36072@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@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