From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] omap: rx51: Fix broken fb on RX51/N900
Date: Wed, 22 Dec 2010 10:57:17 -0800 [thread overview]
Message-ID: <20101222185717.GA7771@atomide.com> (raw)
In-Reply-To: <1293011118.6829.0.camel@tubuntu>
* Tomi Valkeinen <tomi.valkeinen@nokia.com> [101222 01:45]:
> On Wed, 2010-12-22 at 08:56 +0200, ext Jarkko Nikula wrote:
> > On Tue, 21 Dec 2010 12:21:33 -0800
> > Tony Lindgren <tony@atomide.com> wrote:
> >
> > > * Jarkko Nikula <jhnikula@gmail.com> [101221 09:25]:
> > > > Hi
> > > >
> > > > Commit 60d24ee "Added video data to support tvout on rx51" broke the
> > > > framebuffer on N900. Here are two patches where 1st one does a little cleanup
> > > > to be sync with the 2nd fixing the issue. I've tested that both tvout and lcd
> > > > are working.
> > >
> > > Tomi, do you want to pick these three DSS/video related patches from Jarkko?
> > >
> > > If so:
> > >
> > > Acked-by: Tony Lindgren <tony@atomide.com>
> > >
> > > else please ack and let me know if you want me to take them.
> > >
> > I think these should go to linux-omap since the breakage is there and
> > anyway touch only the rx51 board files.
>
> I agree, I don't have that commit in my tree. So Tony, please take the
> patches.
>
> For both patches:
>
> Acked-by: Tomi Valkeinen <tomi.valkeinen@nokia.com>
OK, thanks will queue.
Tony
prev parent reply other threads:[~2010-12-22 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 17:25 [PATCH 0/2] omap: rx51: Fix broken fb on RX51/N900 Jarkko Nikula
2010-12-21 17:25 ` [PATCH 1/2] omap: rx51: Cleanup vdds_sdi supply construction Jarkko Nikula
2010-12-21 17:25 ` [PATCH 2/2] omap: rx51: Add vdda_dac supply for tvout Jarkko Nikula
2010-12-21 20:21 ` [PATCH 0/2] omap: rx51: Fix broken fb on RX51/N900 Tony Lindgren
2010-12-22 6:56 ` Jarkko Nikula
2010-12-22 9:45 ` Tomi Valkeinen
2010-12-22 18:57 ` Tony Lindgren [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=20101222185717.GA7771@atomide.com \
--to=tony@atomide.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).