From: Jani Nikula <jani.nikula@linux.intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>, cgel.zte@gmail.com
Cc: airlied@linux.ie, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
yong yiran <yong.yiran@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [Intel-gfx] [PATCH linux-next] drm/i915/request: Remove unused variables
Date: Mon, 22 Nov 2021 11:09:21 +0200 [thread overview]
Message-ID: <87o86co8u6.fsf@intel.com> (raw)
In-Reply-To: <80173779-5c91-a56e-6bac-ad4ff7c435f7@wanadoo.fr>
On Sun, 21 Nov 2021, Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
> Le 21/11/2021 à 11:13, cgel.zte@gmail.com a écrit :
>> From: yong yiran <yong.yiran@zte.com.cn>
>>
>> The clang_analyzer complains as follows:
>> drivers/gpu/drm/i915/i915_request.c:2119:2 warning:
>> Value stored to 'x' is never read
>>
>> Reported-by: Zeal Robot <zealci@zte.com.cn>
>> Signed-off-by: yong yiran <yong.yiran@zte.com.cn>
The sender's Signed-off-by is missing.
>> ---
>> drivers/gpu/drm/i915/i915_request.c | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
>> index 820a1f38b271..5e4420f461e9 100644
>> --- a/drivers/gpu/drm/i915/i915_request.c
>> +++ b/drivers/gpu/drm/i915/i915_request.c
>> @@ -2047,7 +2047,6 @@ void i915_request_show(struct drm_printer *m,
>> {
>> const char *name = rq->fence.ops->get_timeline_name((struct dma_fence *)&rq->fence);
>> char buf[80] = "";
>> - int x = 0;
>>
>> /*
>> * The prefix is used to show the queue status, for which we use
>> @@ -2079,8 +2078,6 @@ void i915_request_show(struct drm_printer *m,
>> * from the lists
>> */
>>
>> - x = print_sched_attr(&rq->sched.attr, buf, x, sizeof(buf));
>> -
>
> Seriously?
Basically I've started considering all of these patches as static
analyzer reports *only*. The "fixes" have often been completely wrong or
have missed the real issue and merely silenced the warning.
I really couldn't say anything about the "Zeal Robot" itself, but the
patches are giving it a bad reputation.
BR,
Jani.
>
> CJ
>
>
>> drm_printf(m, "%s%.*s%c %llx:%lld%s%s %s @ %dms: %s\n",
>> prefix, indent, " ",
>> queue_status(rq),
>>
>
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>, cgel.zte@gmail.com
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
airlied@linux.ie, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
yong yiran <yong.yiran@zte.com.cn>,
rodrigo.vivi@intel.com, Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] drm/i915/request: Remove unused variables
Date: Mon, 22 Nov 2021 11:09:21 +0200 [thread overview]
Message-ID: <87o86co8u6.fsf@intel.com> (raw)
In-Reply-To: <80173779-5c91-a56e-6bac-ad4ff7c435f7@wanadoo.fr>
On Sun, 21 Nov 2021, Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
> Le 21/11/2021 à 11:13, cgel.zte@gmail.com a écrit :
>> From: yong yiran <yong.yiran@zte.com.cn>
>>
>> The clang_analyzer complains as follows:
>> drivers/gpu/drm/i915/i915_request.c:2119:2 warning:
>> Value stored to 'x' is never read
>>
>> Reported-by: Zeal Robot <zealci@zte.com.cn>
>> Signed-off-by: yong yiran <yong.yiran@zte.com.cn>
The sender's Signed-off-by is missing.
>> ---
>> drivers/gpu/drm/i915/i915_request.c | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
>> index 820a1f38b271..5e4420f461e9 100644
>> --- a/drivers/gpu/drm/i915/i915_request.c
>> +++ b/drivers/gpu/drm/i915/i915_request.c
>> @@ -2047,7 +2047,6 @@ void i915_request_show(struct drm_printer *m,
>> {
>> const char *name = rq->fence.ops->get_timeline_name((struct dma_fence *)&rq->fence);
>> char buf[80] = "";
>> - int x = 0;
>>
>> /*
>> * The prefix is used to show the queue status, for which we use
>> @@ -2079,8 +2078,6 @@ void i915_request_show(struct drm_printer *m,
>> * from the lists
>> */
>>
>> - x = print_sched_attr(&rq->sched.attr, buf, x, sizeof(buf));
>> -
>
> Seriously?
Basically I've started considering all of these patches as static
analyzer reports *only*. The "fixes" have often been completely wrong or
have missed the real issue and merely silenced the warning.
I really couldn't say anything about the "Zeal Robot" itself, but the
patches are giving it a bad reputation.
BR,
Jani.
>
> CJ
>
>
>> drm_printf(m, "%s%.*s%c %llx:%lld%s%s %s @ %dms: %s\n",
>> prefix, indent, " ",
>> queue_status(rq),
>>
>
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>, cgel.zte@gmail.com
Cc: joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
airlied@linux.ie, daniel@ffwll.ch,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, yong yiran <yong.yiran@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [PATCH linux-next] drm/i915/request: Remove unused variables
Date: Mon, 22 Nov 2021 11:09:21 +0200 [thread overview]
Message-ID: <87o86co8u6.fsf@intel.com> (raw)
In-Reply-To: <80173779-5c91-a56e-6bac-ad4ff7c435f7@wanadoo.fr>
On Sun, 21 Nov 2021, Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
> Le 21/11/2021 à 11:13, cgel.zte@gmail.com a écrit :
>> From: yong yiran <yong.yiran@zte.com.cn>
>>
>> The clang_analyzer complains as follows:
>> drivers/gpu/drm/i915/i915_request.c:2119:2 warning:
>> Value stored to 'x' is never read
>>
>> Reported-by: Zeal Robot <zealci@zte.com.cn>
>> Signed-off-by: yong yiran <yong.yiran@zte.com.cn>
The sender's Signed-off-by is missing.
>> ---
>> drivers/gpu/drm/i915/i915_request.c | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
>> index 820a1f38b271..5e4420f461e9 100644
>> --- a/drivers/gpu/drm/i915/i915_request.c
>> +++ b/drivers/gpu/drm/i915/i915_request.c
>> @@ -2047,7 +2047,6 @@ void i915_request_show(struct drm_printer *m,
>> {
>> const char *name = rq->fence.ops->get_timeline_name((struct dma_fence *)&rq->fence);
>> char buf[80] = "";
>> - int x = 0;
>>
>> /*
>> * The prefix is used to show the queue status, for which we use
>> @@ -2079,8 +2078,6 @@ void i915_request_show(struct drm_printer *m,
>> * from the lists
>> */
>>
>> - x = print_sched_attr(&rq->sched.attr, buf, x, sizeof(buf));
>> -
>
> Seriously?
Basically I've started considering all of these patches as static
analyzer reports *only*. The "fixes" have often been completely wrong or
have missed the real issue and merely silenced the warning.
I really couldn't say anything about the "Zeal Robot" itself, but the
patches are giving it a bad reputation.
BR,
Jani.
>
> CJ
>
>
>> drm_printf(m, "%s%.*s%c %llx:%lld%s%s %s @ %dms: %s\n",
>> prefix, indent, " ",
>> queue_status(rq),
>>
>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-11-22 9:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 10:13 [Intel-gfx] [PATCH linux-next] drm/i915/request: Remove unused variables cgel.zte
2021-11-21 10:13 ` cgel.zte
2021-11-21 10:13 ` cgel.zte
2021-11-21 12:18 ` Christophe JAILLET
2021-11-21 12:18 ` [Intel-gfx] " Christophe JAILLET
2021-11-21 12:18 ` Christophe JAILLET
2021-11-21 12:18 ` Christophe JAILLET
2021-11-22 9:09 ` Jani Nikula [this message]
2021-11-22 9:09 ` Jani Nikula
2021-11-22 9:09 ` Jani Nikula
2021-11-22 6:48 ` [Intel-gfx] " kernel test robot
2021-11-22 6:48 ` kernel test robot
2021-11-22 6:48 ` kernel test robot
2021-11-22 7:08 ` [Intel-gfx] " kernel test robot
2021-11-22 7:08 ` kernel test robot
2021-11-22 7:08 ` kernel test robot
2021-11-22 7:08 ` kernel test robot
2021-11-22 14:00 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " 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=87o86co8u6.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=cgel.zte@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yong.yiran@zte.com.cn \
--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 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.