From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PULL for v3.4] SH Mobile LCDC fix
Date: Fri, 18 May 2012 08:57:53 +0000 [thread overview]
Message-ID: <2559608.rGoHhuJBVh@avalon> (raw)
In-Reply-To: <26224047.6PR9YZjWoc@avalon>
Hi Florian,
On Friday 18 May 2012 01:39:19 Florian Tobias Schandinat wrote:
> On 05/17/2012 10:23 PM, Laurent Pinchart wrote:
> > Hi Florian,
> >
> > Is it still possible for the following patch to go to v3.4 ? I've only
> > realized now that MERAM support was broken in some use cases (one of them
> > being fbcon) due to a v3.4-rc regression - thanks to Guennadi Liakhovetski
> > for reporting this.
>
> Umm, I don't like last minute stuff, but this is important enough. BUT...
I don't like it either, I'll add fbcon to my test cases for the future.
> > If this is too late for v3.4 please let me know and I'll CC stable on the
> > patch and resend a pull request for v3.5.
> >
> > The following changes since commit
5e7b911f9a3e582635801675b7fe935b16cd4af5:
> > drivers/video: fsl-diu-fb: don't initialize the THRESHOLDS registers
> >
> > (2012-05-13 13:08:56 +0000)
>
> ...how am I supposed to merge this? It's based on top of all the stuff
> that I plan to ask Linus to pull during the merge window and AFAIK there
> is no way to merge only upper parts of branches. I could cherry-pick it
> but that wouldn't look like a merge or a patch I applied.
Oops, my bad, sorry.
> As this is only a single patch and not much time left, I'd suggest you
> send it directly to Linus (as a patch) with my Ack added to it. Oh and
> make sure to mention that this fixes a regression.
Sure, I'll do that.
Thank you.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2012-05-18 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 22:23 [PULL for v3.4] SH Mobile LCDC fix Laurent Pinchart
2012-05-18 1:39 ` Florian Tobias Schandinat
2012-05-18 8:57 ` Laurent Pinchart [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=2559608.rGoHhuJBVh@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.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.