linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Pitoiset <samuel.pitoiset@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>, David Airlie <airlied@linux.ie>
Cc: Ben Skeggs <bskeggs@redhat.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nouveau: fix nv40_perfctr_next() cleanup regression
Date: Wed, 16 Mar 2016 20:34:57 +0100	[thread overview]
Message-ID: <56E9B561.3060401@gmail.com> (raw)
In-Reply-To: <1457965458-3319933-1-git-send-email-arnd@arndb.de>

Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>

On 03/14/2016 03:24 PM, Arnd Bergmann wrote:
> gcc-6 warns about code in the nouveau driver that is obviously silly:
>
> drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c: In function 'nv40_perfctr_next':
> drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c:62:19: warning: self-comparison always evaluats to false [-Wtautological-compare]
>    if (pm->sequence != pm->sequence) {
>
> The behavior was accidentally introduced in a patch described as "This is
> purely preparation for upcoming commits, there should be no code changes here.".
> As far as I can tell, that was true for the rest of that patch except for
> this one function, which has been changed to a NOP.
>
> This patch restores the original behavior.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: 8c1aeaa13954 ("drm/nouveau/pm: cosmetic changes")
> ---
>   drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c | 6 ++++--
>   1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c b/drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c
> index 4bef72a9d106..3fda594700e0 100644
> --- a/drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c
> +++ b/drivers/gpu/drm/nouveau/nvkm/engine/pm/nv40.c
> @@ -59,9 +59,11 @@ static void
>   nv40_perfctr_next(struct nvkm_pm *pm, struct nvkm_perfdom *dom)
>   {
>   	struct nvkm_device *device = pm->engine.subdev.device;
> -	if (pm->sequence != pm->sequence) {
> +	struct nv40_pm *nv40pm = container_of(pm, struct nv40_pm, base);
> +
> +	if (nv40pm->sequence != pm->sequence) {
>   		nvkm_wr32(device, 0x400084, 0x00000020);
> -		pm->sequence = pm->sequence;
> +		nv40pm->sequence = pm->sequence;
>   	}
>   }
>
>

      parent reply	other threads:[~2016-03-16 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 14:24 [PATCH] nouveau: fix nv40_perfctr_next() cleanup regression Arnd Bergmann
2016-03-16  4:55 ` Ben Skeggs
2016-03-16 19:34 ` Samuel Pitoiset [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=56E9B561.3060401@gmail.com \
    --to=samuel.pitoiset@gmail.com \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).