From: Thierry Reding <thierry.reding@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: drm-next amdgpu warning
Date: Mon, 17 Aug 2015 12:48:16 +0200 [thread overview]
Message-ID: <20150817104815.GD8453@ulmo.nvidia.com> (raw)
In-Reply-To: <CAPM=9tz--89NGjkXjg8C_3gpeSZyo5RhUQ9f=2ud0SOG=dZmUg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 960 bytes --]
On Mon, Aug 17, 2015 at 03:58:10PM +1000, Dave Airlie wrote:
> Hey Alex,
>
> this seems valid,
>
> /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c:
> In function ‘amdgpu_uvd_cs_pass2’:
> /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c:491:17:
> warning: ‘min_ctx_size’ may be used uninitialized in this function
> [-Wmaybe-uninitialized]
> buf_sizes[0x4] = min_ctx_size;
> ^
> /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c:377:58:
> note: ‘min_ctx_size’ was declared here
> unsigned image_size, tmp, min_dpb_size, num_dpb_buffer, min_ctx_size;
> ^
There's a patch for this here:
https://patchwork.kernel.org/patch/7014391/
There's apparently also an internal patch that fixes this, but it wasn't
clear yet which one was going to be picked up.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-08-17 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 5:58 drm-next amdgpu warning Dave Airlie
2015-08-17 10:48 ` Thierry Reding [this message]
2015-08-17 14:33 ` 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=20150817104815.GD8453@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=airlied@gmail.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.