All of lore.kernel.org
 help / color / mirror / Atom feed
From: luis.henriques@canonical.com (Luis Henriques)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] video: mxsfb: Add missing break
Date: Thu, 03 Oct 2013 17:15:33 +0100	[thread overview]
Message-ID: <87bo362uvu.fsf@canonical.com> (raw)
In-Reply-To: <1380601350-6665-1-git-send-email-marex@denx.de> (Marek Vasut's message of "Tue, 1 Oct 2013 06:22:30 +0200")

Marek Vasut <marex@denx.de> writes:

> Add missing break into the restore function.
>
> Upstream commit: 6d0bb818041a02be682abadb3ba35ff608f7d60a
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Cc: stable at vger.kernel.org
>
> ---
>  drivers/video/mxsfb.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/video/mxsfb.c b/drivers/video/mxsfb.c
> index 21223d4..75c5b4e 100644
> --- a/drivers/video/mxsfb.c
> +++ b/drivers/video/mxsfb.c
> @@ -647,6 +647,7 @@ static int mxsfb_restore_mode(struct mxsfb_info *host)
>  		break;
>  	case 3:
>  		bits_per_pixel = 32;
> +		break;
>  	case 1:
>  	default:
>  		return -EINVAL;

Thanks, I believe this fix is applicable to all the stable kernels.
I'm queuing it for the 3.5 kernel.

Cheers,
-- 
Luis

  reply	other threads:[~2013-10-03 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01  4:22 [PATCH] video: mxsfb: Add missing break Marek Vasut
2013-10-03 16:15 ` Luis Henriques [this message]
2013-10-03 16:26   ` Marek Vasut
  -- strict thread matches above, loose matches on Subject: below --
2013-09-26 11:13 Marek Vasut
2013-09-26 11:13 ` Marek Vasut
2013-09-26 12:34 ` Tomi Valkeinen
2013-09-26 12:34   ` Tomi Valkeinen
2013-09-26 13:04   ` Marek Vasut
2013-09-26 13:04     ` Marek Vasut
2013-09-27  3:59     ` Jean-Christophe PLAGNIOL-VILLARD
2013-09-27  3:59       ` Jean-Christophe PLAGNIOL-VILLARD

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=87bo362uvu.fsf@canonical.com \
    --to=luis.henriques@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.