From: Jyri Sarha <jsarha@ti.com>
To: Sean Paul <seanpaul@google.com>, Daniel Schultz <d.schultz@phytec.de>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/tilcdc: fix wrong error handling
Date: Fri, 23 Sep 2016 15:01:13 +0300 [thread overview]
Message-ID: <e0aa79eb-16a8-20a2-757a-b2e247944161@ti.com> (raw)
In-Reply-To: <CAOw6vbLoe+LwQMqCAi9hxPy4TepMe9tPESDANjxyfLv1LozdPg@mail.gmail.com>
On 09/23/16 14:47, Sean Paul wrote:
> On Fri, Sep 23, 2016 at 3:52 AM, Daniel Schultz <d.schultz@phytec.de> wrote:
>> When 'component_bind_all' fails it should not try to unbind components
>> in the error handling. This will produce a null pointer kernel panic when
>> no component exist.
>>
>> This patch changes the order of the error handling. Now, it will only
>> unbind components if the are bound. Otherwise, the module will jump to
>> an error label below.
>>
>> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
>
> Reviewed-by: Sean Paul <seanpaul@chromium.org>
>
Thanks, for both. Should I pick this one :)?
BR,
Jyri
>> ---
>> drivers/gpu/drm/tilcdc/tilcdc_drv.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.c b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
>> index d278093..d491610 100644
>> --- a/drivers/gpu/drm/tilcdc/tilcdc_drv.c
>> +++ b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
>> @@ -315,13 +315,13 @@ fail_irq_uninstall:
>> fail_vblank_cleanup:
>> drm_vblank_cleanup(dev);
>>
>> -fail_mode_config_cleanup:
>> - drm_mode_config_cleanup(dev);
>> -
>> fail_component_cleanup:
>> if (priv->is_componentized)
>> component_unbind_all(dev->dev, dev);
>>
>> +fail_mode_config_cleanup:
>> + drm_mode_config_cleanup(dev);
>> +
>> fail_external_cleanup:
>> tilcdc_remove_external_encoders(dev);
>>
>> --
>> 1.9.1
>>
next prev parent reply other threads:[~2016-09-23 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 10:52 Daniel Schultz
2016-09-23 11:47 ` Sean Paul
2016-09-23 12:01 ` Jyri Sarha [this message]
2016-09-23 12:01 ` Sean Paul
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=e0aa79eb-16a8-20a2-757a-b2e247944161@ti.com \
--to=jsarha@ti.com \
--cc=airlied@linux.ie \
--cc=d.schultz@phytec.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@google.com \
--cc=tomi.valkeinen@ti.com \
/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
all inboxes | Powered by JetHome®