From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"Garg, Nemesa" <nemesa.garg@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Garg, Nemesa" <nemesa.garg@intel.com>
Subject: RE: [PATCH] drm/i915/scaler: Fix for WA_14011503117
Date: Thu, 07 Aug 2025 12:57:05 +0300 [thread overview]
Message-ID: <df0adbad51530c1da1fcd23ccb06b5158e013738@intel.com> (raw)
In-Reply-To: <DM3PPF208195D8DE1EF756F38B634FBF9BCE32CA@DM3PPF208195D8D.namprd11.prod.outlook.com>
On Thu, 07 Aug 2025, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> Subject: [PATCH] drm/i915/scaler: Fix for WA_14011503117
>
> We already have a commit with that name don't really want many commits with the same subject
>
>>
>> Remove the redundant check statement.
>
> The is statement is not redundant just wrong will need to fix the commit description
>
>>
>> v2: Add scaler_id check [Jani]
>>
>> Fixes: 73309ed9d598 ("drm/i915/display: WA_14011503117")
>> Signed-off-by: Nemesa Garg <nemesa.garg@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/skl_scaler.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/skl_scaler.c
>> b/drivers/gpu/drm/i915/display/skl_scaler.c
>> index cd7ebbeb9508..6891a0b00f41 100644
>> --- a/drivers/gpu/drm/i915/display/skl_scaler.c
>> +++ b/drivers/gpu/drm/i915/display/skl_scaler.c
>> @@ -960,7 +960,7 @@ void adl_scaler_ecc_unmask(const struct
>> intel_crtc_state *crtc_state)
>> const struct intel_crtc_scaler_state *scaler_state =
>> &crtc_state->scaler_state;
>>
>> - if (!scaler_state && scaler_state->scaler_id == -1)
>> + if (scaler_state->scaler_id == -1)
>
> Hmm but what if scaler_state ends up being null now
It can't be NULL.
>
> This should have been scaler_state && scaler_state->scaler_id ==
> Also please add people who had bought this issue up in cc to keep them in loop in this case that would be Jani.
> It's very easy to miss fixes like this in all the mails that end up getting sent upstream more so if they are not cc'ed
>
> Regards,
> Suraj Kandpal
>> return;
>>
>> intel_de_write_fw(display,
>> --
>> 2.25.1
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-08-07 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 10:19 [PATCH] drm/i915/scaler: Fix for WA_14011503117 Nemesa Garg
2025-08-06 17:23 ` ✗ i915.CI.BAT: failure for drm/i915/scaler: Fix for WA_14011503117 (rev2) Patchwork
2025-08-07 6:12 ` ✓ i915.CI.BAT: success " Patchwork
2025-08-07 8:04 ` ✗ i915.CI.Full: failure " Patchwork
2025-08-07 9:12 ` ✓ i915.CI.Full: success " Patchwork
2025-08-07 9:45 ` [PATCH] drm/i915/scaler: Fix for WA_14011503117 Kandpal, Suraj
2025-08-07 9:57 ` Jani Nikula [this message]
2025-08-07 9:59 ` Kandpal, Suraj
-- strict thread matches above, loose matches on Subject: below --
2025-08-06 9:03 Nemesa Garg
2025-08-06 9:10 ` Jani Nikula
2025-08-06 9:20 ` Garg, Nemesa
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=df0adbad51530c1da1fcd23ccb06b5158e013738@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nemesa.garg@intel.com \
--cc=suraj.kandpal@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.