From: Paul Mundt <lethal@linux-sh.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: lo-ml <linux-omap@vger.kernel.org>,
lfbdev-ml <linux-fbdev@vger.kernel.org>
Subject: Re: [GIT PULL] OMAP DSS updates for 2.6.40
Date: Tue, 24 May 2011 06:38:05 +0000 [thread overview]
Message-ID: <20110524063803.GC11986@linux-sh.org> (raw)
In-Reply-To: <1306151004.1871.36.camel@deskari>
On Mon, May 23, 2011 at 02:43:24PM +0300, Tomi Valkeinen wrote:
> Here are the OMAP Display Subsystem updates for 2.6.40.
>
> Most of the patches are OMAP4 related, either fixing the old code to
> allow us to implement new OMAP4 features, or implementing those new
> features. Other bigger changes are ULPS power management feature and
> moving the DSS header file from arch/arm/plat-omap/include to
> include/video.
>
Pulled and pushed out, thanks. There were a couple of conflicts, so you
may want to doublecheck to make sure nothing was inadvertently broken.
next prev parent reply other threads:[~2011-05-24 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 11:43 [GIT PULL] OMAP DSS updates for 2.6.40 Tomi Valkeinen
2011-05-24 6:38 ` Paul Mundt [this message]
2011-05-24 9:37 ` Tomi Valkeinen
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=20110524063803.GC11986@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
/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).