From: "Christian König" <christian.koenig@amd.com>
To: Julia Lawall <Julia.Lawall@lip6.fr>,
Alex Deucher <alexander.deucher@amd.com>
Cc: kernel-janitors@vger.kernel.org,
"David (ChunMing) Zhou" <David1.Zhou@amd.com>,
David Airlie <airlied@linux.ie>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: adjust tested variable
Date: Sun, 28 Jan 2018 14:03:31 +0100 [thread overview]
Message-ID: <f6ee63cc-0d2e-d314-1621-dd9045970ada@amd.com> (raw)
In-Reply-To: <1517063295-16648-1-git-send-email-Julia.Lawall@lip6.fr>
Am 27.01.2018 um 15:28 schrieb Julia Lawall:
> Check the variable that was most recently initialized.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression x, y, f, g, e, m;
> statement S1,S2,S3,S4;
> @@
>
> x = f(...);
> if (\(<+...x...+>\&e\)) S1 else S2
> (
> x = g(...);
> |
> m = g(...,&x,...);
> |
> y = g(...);
> *if (e)
> S3 else S4
> )
> // </smpl>
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Good catch, added my rb and pushed it into our to-be-upstreamed branch.
Thanks,
Christian.
>
> ---
> drivers/gpu/drm/radeon/radeon_uvd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_uvd.c b/drivers/gpu/drm/radeon/radeon_uvd.c
> index d34d1cf..95f4db7 100644
> --- a/drivers/gpu/drm/radeon/radeon_uvd.c
> +++ b/drivers/gpu/drm/radeon/radeon_uvd.c
> @@ -995,7 +995,7 @@ int radeon_uvd_calc_upll_dividers(struct radeon_device *rdev,
> /* calc dclk divider with current vco freq */
> dclk_div = radeon_uvd_calc_upll_post_div(vco_freq, dclk,
> pd_min, pd_even);
> - if (vclk_div > pd_max)
> + if (dclk_div > pd_max)
> break; /* vco is too big, it has to stop */
>
> /* calc score with current vco freq */
>
prev parent reply other threads:[~2018-01-28 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 14:28 Julia Lawall
2018-01-28 13:03 ` Christian König [this message]
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=f6ee63cc-0d2e-d314-1621-dd9045970ada@amd.com \
--to=christian.koenig@amd.com \
--cc=David1.Zhou@amd.com \
--cc=Julia.Lawall@lip6.fr \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®