From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
linux-fbdev <linux-fbdev@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] fbdev fixes for 3.9
Date: Thu, 28 Mar 2013 12:26:37 +0000 [thread overview]
Message-ID: <515436FD.6020004@ti.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
Hi Linus,
Since Florian is still away/inactive, I volunteered to collect fbdev fixes for
3.9 and changes for 3.10. I didn't receive any other fbdev fixes than OMAP yet,
but I didn't want to delay this further as there's a compilation fix for OMAP1.
So there could be still some fbdev fixes on the way a bit later.
Tomi
The following changes since commit a937536b868b8369b98967929045f1df54234323:
Linux 3.9-rc3 (2013-03-17 15:59:32 -0700)
are available in the git repository at:
git://gitorious.org/linux-omap-dss2/linux.git tags/fbdev-fixes-3.9-rc4
for you to fetch changes up to ff588d83bf12fe05521a64e85dd4e2b848c0b20d:
omapdss: features: fix supported outputs for OMAP4 (2013-03-22 10:14:32 +0200)
----------------------------------------------------------------
* Fix OMAP1 compilation
* OMAP display fixes
----------------------------------------------------------------
Aaro Koskinen (1):
omapfb: fix broken build on OMAP1
Archit Taneja (1):
omapdss: features: fix supported outputs for OMAP4
Grazvydas Ignotas (1):
OMAPDSS: tpo-td043 panel: fix data passing between SPI/DSS parts
drivers/video/omap/omapfb_main.c | 2 ++
drivers/video/omap2/displays/panel-tpo-td043mtea1.c | 13 +++++++++++--
drivers/video/omap2/dss/dss_features.c | 6 ++----
3 files changed, 15 insertions(+), 6 deletions(-)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
reply other threads:[~2013-03-28 12:26 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=515436FD.6020004@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@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).