From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] video: mxsfb: Add missing break
Date: Thu, 3 Oct 2013 18:26:11 +0200 [thread overview]
Message-ID: <201310031826.11531.marex@denx.de> (raw)
In-Reply-To: <87bo362uvu.fsf@canonical.com>
Dear Luis Henriques,
> 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.
Thanks!
btw. it'd be nice if you could push the kernel.ubuntu.com admins to fix their
git server ( https://bugs.launchpad.net/ubuntu/+source/git/+bug/1228148 ) ;-)
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-10-03 16:26 UTC|newest]
Thread overview: 7+ 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
2013-10-03 16:26 ` Marek Vasut [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-26 11:13 Marek Vasut
2013-09-26 12:34 ` Tomi Valkeinen
2013-09-26 13:04 ` Marek Vasut
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=201310031826.11531.marex@denx.de \
--to=marex@denx.de \
--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 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).