From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-fbdev <linux-fbdev@vger.kernel.org>linux-omap
<linux-omap@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] omapdss fixes for 3.8
Date: Thu, 14 Feb 2013 17:27:21 +0000 [thread overview]
Message-ID: <511D1E79.8030909@ti.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
Hi Linus,
It'd be great if these two late fixes would still make it into 3.8. The other
one fixes ARM kernel compilation when using 'allyesconfig', and the other makes
DPI displays function again on OMAP3630 boards.
Tomi
The following changes since commit 836dc9e3fbbab0c30aa6e664417225f5c1fb1c39:
Linux 3.8-rc7 (2013-02-09 08:20:39 +1100)
are available in the git repository at:
git://gitorious.org/linux-omap-dss2/linux.git tags/omapdss-for-3.8-rc8
for you to fetch changes up to 91e83ffd6d3ba4de21202b4f541777a7a8db02c8:
omapdrm: fix the dependency to omapdss (2013-02-14 13:08:29 +0200)
----------------------------------------------------------------
* Fix ARM compilation with "allyesconfig" (omapdrm: fix the dependency to
omapdss)
* fix DPI displays on OMAP3630 (OMAPDSS: add FEAT_DPI_USES_VDDS_DSI to
omap3630_dss_feat_list)
----------------------------------------------------------------
NeilBrown (1):
OMAPDSS: add FEAT_DPI_USES_VDDS_DSI to omap3630_dss_feat_list
Tomi Valkeinen (1):
omapdrm: fix the dependency to omapdss
drivers/staging/omapdrm/Kconfig | 2 +-
drivers/video/omap2/dss/dss_features.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
reply other threads:[~2013-02-14 17:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=511D1E79.8030909@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=torvalds@linux-foundation.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).