From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [patch] fbdev: ssd1307fb: potential ERR_PTR dereference
Date: Mon, 25 May 2015 05:40:07 +0000 [thread overview]
Message-ID: <5562B5B7.3060701@ti.com> (raw)
In-Reply-To: <20150523173235.GA31595@mwanda>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
On 23/05/15 20:32, Dan Carpenter wrote:
> The error handling got shifted down a few lines from where it was
> supposed to be for some reason.
>
> Fixes: a14a7ba8cb0f ('fbdev: ssd1307fb: add backlight controls for setting the contrast')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/drivers/video/fbdev/ssd1307fb.c b/drivers/video/fbdev/ssd1307fb.c
> index 8fc224c..9c28a77 100644
> --- a/drivers/video/fbdev/ssd1307fb.c
> +++ b/drivers/video/fbdev/ssd1307fb.c
> @@ -655,15 +655,16 @@ static int ssd1307fb_probe(struct i2c_client *client,
> snprintf(bl_name, sizeof(bl_name), "ssd1307fb%d", info->node);
> bl = backlight_device_register(bl_name, &client->dev, par,
> &ssd1307fb_bl_ops, NULL);
> - bl->props.brightness = par->contrast;
> - bl->props.max_brightness = MAX_CONTRAST;
> - info->bl_dev = bl;
> -
> if (IS_ERR(bl)) {
> dev_err(&client->dev, "unable to register backlight device: %ld\n",
> PTR_ERR(bl));
> goto bl_init_error;
> }
> +
> + bl->props.brightness = par->contrast;
> + bl->props.max_brightness = MAX_CONTRAST;
> + info->bl_dev = bl;
> +
> dev_info(&client->dev, "fb%d: %s framebuffer device registered, using %d bytes of video memory\n", info->node, info->fix.id, vmem_size);
>
> return 0;
>
Thanks, queued for 4.2.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-05-25 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 17:32 [patch] fbdev: ssd1307fb: potential ERR_PTR dereference Dan Carpenter
2015-05-24 7:19 ` Maxime Ripard
2015-05-25 5:40 ` Tomi Valkeinen [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=5562B5B7.3060701@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-fbdev@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).