From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0
Date: Mon, 18 Mar 2013 14:58:17 +0100 [thread overview]
Message-ID: <201303181458.17656.marex@denx.de> (raw)
In-Reply-To: <20130318130108.GE12462@S2101-09.ap.freescale.net>
Dear Shawn Guo,
> On Mon, Mar 18, 2013 at 10:11:47AM -0300, Fabio Estevam wrote:
> > Shawn Guo wrote:
> > > Since it touches mach-mxs as well, let me send it through arm-soc tree
> > > as fix for 3.9.
> >
> > Please CC stable as well, so that we can have X11 functional with 3.8.
>
> Ok, done.
Shawn, I think this patch applies to 3.9-rc but there's one more platform in
mach-mxs.c in 3.9-rc thus this will have compile issue. Just renaming those two
FB_SYNC_ values to MXSFB_SYNC_ fixes the compile issue on 3.9-rc. Also the
commit log doesn't look all that cool .... I probably should have marked the
patch as RFC.
Shall I send you one for 3.9-rc and one for stable maybe ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-03-18 13:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 20:09 Shifted framebuffer after X11 starts on mx28 Fabio Estevam
2013-03-16 20:55 ` Marek Vasut
2013-03-16 21:00 ` Marek Vasut
2013-03-16 22:06 ` [PATCH] ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0 Marek Vasut
2013-03-16 22:38 ` Fabio Estevam
2013-03-18 12:44 ` Shawn Guo
2013-03-18 13:11 ` Fabio Estevam
2013-03-18 13:01 ` Shawn Guo
2013-03-18 13:58 ` Marek Vasut [this message]
2013-03-18 14:06 ` Shawn Guo
2013-03-18 14:18 ` Marek Vasut
2013-03-18 14:31 ` Shawn Guo
2013-03-18 15:19 ` Marek Vasut
2013-03-19 5:48 ` Shawn Guo
2013-03-19 10:33 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2013-03-18 18:23 Marek Vasut
2013-03-18 18:58 ` Greg KH
2013-03-18 21:31 ` Marek Vasut
2013-03-18 22:01 ` Jonathan Nieder
2013-03-18 22:17 ` Marek Vasut
2013-03-18 18:24 Marek Vasut
2013-03-19 5:51 ` Shawn Guo
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=201303181458.17656.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).