From: Daniel Vetter <daniel@ffwll.ch>
To: Insu Yun <wuninsu@gmail.com>
Cc: airlied@linux.ie, daniel.vetter@ffwll.ch,
ville.syrjala@linux.intel.com, alexander.deucher@amd.com,
treding@nvidia.com, boris.brezillon@free-electrons.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
taesoo@gatech.edu, yeongjin.jang@gatech.edu, insu@gatech.edu,
changwoo@gatech.edu
Subject: Re: [PATCH] ch7006: correctly handling failed allocation
Date: Tue, 9 Feb 2016 10:22:20 +0100 [thread overview]
Message-ID: <20160209092220.GC11240@phenom.ffwll.local> (raw)
In-Reply-To: <1454025276-13465-1-git-send-email-wuninsu@gmail.com>
On Thu, Jan 28, 2016 at 06:54:36PM -0500, Insu Yun wrote:
> Since drm_property_create_range can be failed in memory pressure,
> it needs to be checked and return -ENOMEM.
>
> Signed-off-by: Insu Yun <wuninsu@gmail.com>
Applied to drm-misc, thanks.
-Daniel
> ---
> drivers/gpu/drm/i2c/ch7006_drv.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i2c/ch7006_drv.c b/drivers/gpu/drm/i2c/ch7006_drv.c
> index 90db5f4..0594c45 100644
> --- a/drivers/gpu/drm/i2c/ch7006_drv.c
> +++ b/drivers/gpu/drm/i2c/ch7006_drv.c
> @@ -253,6 +253,8 @@ static int ch7006_encoder_create_resources(struct drm_encoder *encoder,
> drm_mode_create_tv_properties(dev, NUM_TV_NORMS, ch7006_tv_norm_names);
>
> priv->scale_property = drm_property_create_range(dev, 0, "scale", 0, 2);
> + if (!priv->scale_property)
> + return -ENOMEM;
>
> drm_object_attach_property(&connector->base, conf->tv_select_subconnector_property,
> priv->select_subconnector);
> --
> 1.9.1
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2016-02-09 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 23:54 [PATCH] ch7006: correctly handling failed allocation Insu Yun
2016-02-09 9:22 ` Daniel Vetter [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=20160209092220.GC11240@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=boris.brezillon@free-electrons.com \
--cc=changwoo@gatech.edu \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=insu@gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=taesoo@gatech.edu \
--cc=treding@nvidia.com \
--cc=ville.syrjala@linux.intel.com \
--cc=wuninsu@gmail.com \
--cc=yeongjin.jang@gatech.edu \
/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