From: Ben Skeggs <bskeggs@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: drm/nv50-/disp: audit and version DAC_LOAD method
Date: Wed, 13 Aug 2014 19:30:40 -0400 (EDT) [thread overview]
Message-ID: <367116909.42724148.1407972640288.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20140813112916.GA24203@mwanda>
----- Original Message -----
> From: "Dan Carpenter" <dan.carpenter@oracle.com>
> To: bskeggs@redhat.com
> Cc: dri-devel@lists.freedesktop.org
> Sent: Wednesday, 13 August, 2014 9:29:16 PM
> Subject: re: drm/nv50-/disp: audit and version DAC_LOAD method
>
> Hello Ben Skeggs,
>
> The patch c4abd3178e11: "drm/nv50-/disp: audit and version DAC_LOAD
> method" from Aug 10, 2014, leads to the following static checker
> warning:
>
> drivers/gpu/drm/nouveau/core/engine/disp/dacnv50.c:78 nv50_dac_sense()
> warn: 0xfff00000 is larger than 16 bits
There was a mess-up when I cleaned up the structs, I've got a fix in my tree that I'll get to Linus in -fixes.
Thanks,
Ben.
>
> drivers/gpu/drm/nouveau/core/engine/disp/dacnv50.c
> 65 nv50_dac_sense(NV50_DISP_MTHD_V1)
> 66 {
> 67 union {
> 68 struct nv50_disp_dac_load_v0 v0;
> 69 } *args = data;
> 70 const u32 doff = outp->or * 0x800;
> 71 u32 loadval;
> 72 int ret;
> 73
> 74 nv_ioctl(object, "disp dac load size %d\n", size);
> 75 if (nvif_unpack(args->v0, 0, 0, false)) {
> 76 nv_ioctl(object, "disp dac load vers %d data %08x\n",
> 77 args->v0.version, args->v0.data);
> 78 if (args->v0.data & 0xfff00000)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> This condition can't be true. It's not clear what was intended.
>
> 79 return -EINVAL;
> 80 loadval = args->v0.data;
> 81 } else
> 82 return ret;
>
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2014-08-13 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 11:29 drm/nv50-/disp: audit and version DAC_LOAD method Dan Carpenter
2014-08-13 23:30 ` Ben Skeggs [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=367116909.42724148.1407972640288.JavaMail.zimbra@redhat.com \
--to=bskeggs@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.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 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.