From: Jani Nikula <jani.nikula@intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>,
"Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH] Revert "FIXME: drm/i915/ips: apparently silence warnings"
Date: Wed, 27 Sep 2023 09:59:30 +0300 [thread overview]
Message-ID: <874jjgksod.fsf@intel.com> (raw)
In-Reply-To: <DM4PR11MB6360B7F6C270EC1BA6E35EA1F4C2A@DM4PR11MB6360.namprd11.prod.outlook.com>
On Wed, 27 Sep 2023, "Shankar, Uma" <uma.shankar@intel.com> wrote:
>> -----Original Message-----
>> From: Borah, Chaitanya Kumar <chaitanya.kumar.borah@intel.com>
>> Sent: Monday, September 18, 2023 12:43 PM
>> To: intel-xe@lists.freedesktop.org
>> Cc: Borah, Chaitanya Kumar <chaitanya.kumar.borah@intel.com>; Nikula, Jani
>> <jani.nikula@intel.com>; Shankar, Uma <uma.shankar@intel.com>
>> Subject: [PATCH] Revert "FIXME: drm/i915/ips: apparently silence warnings"
>>
>> This reverts commit 004360063d3b8a29cdf599ed18dc6a23c6e61513.
>>
>> There seems to be no effect of this patch i.e. removing this patch yields no
>> compiler warnings. Hence, revert.
>
> Hi Jani,
> Reverting the change is not resulting in any warnings. Do we really need it or
> are we missing something.
It may have been fixed by earlier changes. If it builds, it's good.
BR,
Jani.
>
> Regards,
> Uma Shankar
>
>> Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
>>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>> Cc: Uma Shankar <uma.shankar@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_display.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c
>> b/drivers/gpu/drm/i915/display/intel_display.c
>> index 9df8081f78d9..d0ec09621fe4 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
>> @@ -4195,8 +4195,8 @@ static u16 hsw_linetime_wm(const struct
>> intel_crtc_state *crtc_state)
>> return min(linetime_wm, 0x1ff);
>> }
>>
>> -static inline u16 hsw_ips_linetime_wm(const struct intel_crtc_state *crtc_state,
>> - const struct intel_cdclk_state *cdclk_state)
>> +static u16 hsw_ips_linetime_wm(const struct intel_crtc_state *crtc_state,
>> + const struct intel_cdclk_state *cdclk_state)
>> {
>> const struct drm_display_mode *pipe_mode =
>> &crtc_state->hw.pipe_mode;
>> @@ -4239,7 +4239,7 @@ static int hsw_compute_linetime_wm(struct
>> intel_atomic_state *state,
>> struct drm_i915_private *dev_priv = to_i915(crtc->base.dev);
>> struct intel_crtc_state *crtc_state =
>> intel_atomic_get_new_crtc_state(state, crtc);
>> - __maybe_unused const struct intel_cdclk_state *cdclk_state;
>> + const struct intel_cdclk_state *cdclk_state;
>>
>> if (DISPLAY_VER(dev_priv) >= 9)
>> crtc_state->linetime = skl_linetime_wm(crtc_state);
>> --
>> 2.25.1
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-09-27 7:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 7:12 [Intel-xe] [PATCH] Revert "FIXME: drm/i915/ips: apparently silence warnings" Chaitanya Kumar Borah
2023-09-27 5:36 ` Shankar, Uma
2023-09-27 6:59 ` Jani Nikula [this message]
2023-09-27 10:08 ` [Intel-xe] ✓ CI.Patch_applied: success for Revert "FIXME: drm/i915/ips: apparently silence warnings" (rev2) Patchwork
2023-09-27 10:08 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-27 10:09 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-27 10:16 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-27 10:16 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-27 10:18 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-27 10:50 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-10-10 12:19 [Intel-xe] [PATCH] Revert "FIXME: drm/i915/ips: apparently silence warnings" Chaitanya Kumar Borah
2023-10-11 8:54 ` Shankar, Uma
2023-10-12 3:41 ` Shankar, Uma
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=874jjgksod.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=uma.shankar@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