From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>, cgel.zte@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
luo penghao <luo.penghao@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [Intel-gfx] [PATCH linux-next] drm/i915/display: Delete redundant post_mask assignment
Date: Wed, 08 Dec 2021 15:20:15 +0200 [thread overview]
Message-ID: <87lf0v44j4.fsf@intel.com> (raw)
In-Reply-To: <YbCtUZUSbEpCuDoi@intel.com>
On Wed, 08 Dec 2021, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Wed, Dec 08, 2021 at 07:46:19AM +0000, cgel.zte@gmail.com wrote:
>> From: luo penghao <luo.penghao@zte.com.cn>
>>
>> This value will be overwritten by the following if statement, even
>> if the if is not executed, the value will not be used
>>
>> The clang_analyzer complains as follows:
>>
>> Value stored to 'port_mask' is never read
>>
>> Reported-by: Zeal Robot <zealci@zte.com.cn>
>> Signed-off-by: luo penghao <luo.penghao@zte.com.cn>
>> ---
>> drivers/gpu/drm/i915/display/intel_ddi.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c b/drivers/gpu/drm/i915/display/intel_ddi.c
>> index bd18432..3aad0c3 100644
>> --- a/drivers/gpu/drm/i915/display/intel_ddi.c
>> +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
>> @@ -2011,7 +2011,6 @@ void intel_ddi_sanitize_encoder_pll_mapping(struct intel_encoder *encoder)
>> return;
>> }
>>
>> - port_mask = BIT(encoder->port);
>> ddi_clk_needed = encoder->base.crtc;
>>
>> if (encoder->type == INTEL_OUTPUT_DSI) {
>
> 'port_mask' declaration could now be moved into this block.
I've basically given up on patches from cgel.zte@gmail.com,
luo.penghao@zte.com.cn, zealci@zte.com.cn, etc. The patches are the
simplest possible changes to silence static analyzer warnings, with no
further analysis of the issues, and no follow-up on questions.
Until that changes, I think we're better off just regarding them static
as analyzer reports.
BR,
Jani.
>
>> --
>> 2.15.2
>>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-12-08 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 7:46 [Intel-gfx] [PATCH linux-next] drm/i915/display: Delete redundant post_mask assignment cgel.zte
2021-12-08 13:04 ` Ville Syrjälä
2021-12-08 13:20 ` Jani Nikula [this message]
2021-12-08 14:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-12-08 18:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87lf0v44j4.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=cgel.zte@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luo.penghao@zte.com.cn \
--cc=sfr@canb.auug.org.au \
--cc=ville.syrjala@linux.intel.com \
--cc=zealci@zte.com.cn \
/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