From: Jonathan Nieder <jrnieder@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0
Date: Mon, 18 Mar 2013 22:01:34 +0000	[thread overview]
Message-ID: <20130318220134.GC5062@elie.Belkin> (raw)
In-Reply-To: <201303182231.22749.marex@denx.de>
Marek Vasut wrote:
>  - It or an equivalent fix must already exist in Linus' tree (upstream).
> This can not happen, the fix in Linus' tree will have to be different since in 
> v3.9 there is one more MX28 platform which also needs fixing. I suppose I will 
> now wait for Shawn to merge the patch for 3.9-rc, get it mainline and then this 
> one can be merged?
Yes, please write again with a patch referencing the upstream commit
id when this has been fixed upstream.
Thanks and hope that helps,
Jonathan
next prev parent reply	other threads:[~2013-03-18 22:01 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 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 [this message]
2013-03-18 22:17             ` Marek Vasut
2013-03-18 18:24     ` Marek Vasut
2013-03-19  5:51       ` Shawn Guo
2013-03-18 12:44   ` Shawn Guo
2013-03-18 12:52     ` Fabio Estevam
2013-03-18 13:01       ` Shawn Guo
2013-03-18 13:58         ` Marek Vasut
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
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=20130318220134.GC5062@elie.Belkin \
    --to=jrnieder@gmail.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 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).