From: Scott Wood <scottwood@freescale.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v3] video: fbdev: fsl: Fix kernel crash when diu_ops is not implemented
Date: Mon, 07 Dec 2015 17:07:22 +0000 [thread overview]
Message-ID: <1449508042.15946.56.camel@freescale.com> (raw)
In-Reply-To: <1449107652-5134-1-git-send-email-dongsheng.wang@freescale.com>
On Thu, 2015-12-03 at 09:54 +0800, Dongsheng Wang wrote:
> From: Wang Dongsheng <dongsheng.wang@freescale.com>
>
> If diu_ops is not implemented on platform, kernel will access a NULL
> pointer. We need to check this pointer in DIU initialization.
>
> Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
> ---
> v3:
> - Fix capitalization in patch description.
> - Add comments for verify diu_ops.set_pixel_clock.
>
> v2:
> - Move set_pixel_clock judgement to fsl_diu_init.
>
> drivers/video/fbdev/fsl-diu-fb.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
Why did you not CC stable as I previously requested?
-Scott
prev parent reply other threads:[~2015-12-07 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 1:54 [PATCH v3] video: fbdev: fsl: Fix kernel crash when diu_ops is not implemented Dongsheng Wang
2015-12-03 14:03 ` Timur Tabi
2015-12-07 16:57 ` Tomi Valkeinen
2015-12-07 17:07 ` Scott Wood [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=1449508042.15946.56.camel@freescale.com \
--to=scottwood@freescale.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).