From: Harry Wentland <hwentlan@amd.com>
To: YueHaibing <yuehaibing@huawei.com>,
"Wentland, Harry" <Harry.Wentland@amd.com>,
"Li, Sun peng (Leo)" <Sunpeng.Li@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"Zhou, David(ChunMing)" <David1.Zhou@amd.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"Lakha, Bhawanpreet" <Bhawanpreet.Lakha@amd.com>,
"Koo, Anthony" <Anthony.Koo@amd.com>,
"Cyr, Aric" <Aric.Cyr@amd.com>,
"Harmanprit.Tatla@amd.com" <Harmanprit.Tatla@amd.com>,
"bayan.zabihiyan@amd.com" <bayan.zabihiyan@amd.com>,
"Othman, Ahmad" <Ahmad.Othman@amd.com>,
"Amini, Reza" <Reza.Amini@amd.com>
Cc: "amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] drm/amd/display: remove set but not used variable 'core_freesync'
Date: Mon, 7 Oct 2019 14:06:46 +0000 [thread overview]
Message-ID: <db644945-24df-7d67-7fc6-880833466593@amd.com> (raw)
In-Reply-To: <20191006105735.60708-1-yuehaibing@huawei.com>
On 2019-10-06 6:57 a.m., YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> rivers/gpu/drm/amd/amdgpu/../display/modules/freesync/freesync.c:
> In function mod_freesync_get_settings:
> drivers/gpu/drm/amd/amdgpu/../display/modules/freesync/freesync.c:984:24:
> warning: variable core_freesync set but not used [-Wunused-but-set-variable]
>
> It is not used since commit 98e6436d3af5 ("drm/amd/display: Refactor FreeSync module")
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Harry
> ---
> drivers/gpu/drm/amd/display/modules/freesync/freesync.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/modules/freesync/freesync.c b/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
> index 9ce56a8..237dda7 100644
> --- a/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
> +++ b/drivers/gpu/drm/amd/display/modules/freesync/freesync.c
> @@ -981,13 +981,9 @@ void mod_freesync_get_settings(struct mod_freesync *mod_freesync,
> unsigned int *inserted_frames,
> unsigned int *inserted_duration_in_us)
> {
> - struct core_freesync *core_freesync = NULL;
> -
> if (mod_freesync == NULL)
> return;
>
> - core_freesync = MOD_FREESYNC_TO_CORE(mod_freesync);
> -
> if (vrr->supported) {
> *v_total_min = vrr->adjust.v_total_min;
> *v_total_max = vrr->adjust.v_total_max;
>
next prev parent reply other threads:[~2019-10-07 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 10:57 YueHaibing
2019-10-07 14:06 ` Harry Wentland [this message]
2019-10-07 15:57 ` Alex Deucher
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=db644945-24df-7d67-7fc6-880833466593@amd.com \
--to=hwentlan@amd.com \
--cc=Ahmad.Othman@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Anthony.Koo@amd.com \
--cc=Aric.Cyr@amd.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=David1.Zhou@amd.com \
--cc=Harmanprit.Tatla@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Reza.Amini@amd.com \
--cc=Sunpeng.Li@amd.com \
--cc=airlied@linux.ie \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bayan.zabihiyan@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@huawei.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
all inboxes | Powered by JetHome®