From: Gerd Hoffmann <kraxel@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: kernel-janitors@vger.kernel.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
Dave Airlie <airlied@redhat.com>,
Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Subject: Re: [PATCH] drm: qxl: add missing return check
Date: Tue, 14 Mar 2017 12:02:22 +0100 [thread overview]
Message-ID: <1489489342.27633.3.camel@redhat.com> (raw)
In-Reply-To: <20170314075410.GB5984@mwanda>
On Di, 2017-03-14 at 10:54 +0300, Dan Carpenter wrote:
> My static checker complains that "release" is uninitialized if
> qxl_alloc_release_reserved() fails, so let's add a check for that.
applied to drm-misc-next.
thanks,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-03-14 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 7:54 [PATCH] drm: qxl: add missing return check Dan Carpenter
2017-03-14 11:02 ` Gerd Hoffmann [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=1489489342.27633.3.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=krisman@collabora.co.uk \
--cc=virtualization@lists.linux-foundation.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