public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] omapfb: Add sanity check to omapfb_update_window_async
Date: Fri, 26 Jan 2007 13:54:08 -0800	[thread overview]
Message-ID: <20070126215408.GM29286@atomide.com> (raw)
In-Reply-To: <858xg5g236.fsf@orfeo.duckcorp.org>

* Arnaud Patard <arnaud.patard@rtp-net.org> [070114 05:45]:
> 
> This patch makes sure that the fb_info pointer given to
> omapfb_update_window_async is not null.
> 
> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
> ---

> ---
>  drivers/video/omap/omapfb_main.c |    9 	7 +	2 -	0 !
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> Index: linux-omap-2.6/drivers/video/omap/omapfb_main.c
> ===================================================================
> --- linux-omap-2.6.orig/drivers/video/omap/omapfb_main.c	2007-01-14 14:10:26.000000000 +0100
> +++ linux-omap-2.6/drivers/video/omap/omapfb_main.c	2007-01-14 14:10:29.000000000 +0100
> @@ -626,10 +626,15 @@ int omapfb_update_window_async(struct fb
>  				void (*callback)(void *),
>  				void *callback_data)
>  {
> -	struct omapfb_plane_struct *plane = fbi->par;
> -	struct omapfb_device *fbdev = plane->fbdev;
> +	struct omapfb_plane_struct *plane;
> +	struct omapfb_device *fbdev;
>  	struct fb_var_screeninfo *var;
>  
> +	if (!fbi)
> +		return -EINVAL;
> +
> +	plane = fbi->par;
> +	fbdev = plane->fbdev;
>  	var = &fbi->var;
>  
>  	if (win->x >= var->xres || win->y >= var->yres)

Pushing today.

Tony

      reply	other threads:[~2007-01-26 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 13:38 [PATCH] omapfb: Add sanity check to omapfb_update_window_async Arnaud Patard
2007-01-26 21:54 ` Tony Lindgren [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=20070126215408.GM29286@atomide.com \
    --to=tony@atomide.com \
    --cc=arnaud.patard@rtp-net.org \
    --cc=linux-omap-open-source@linux.omap.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