linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	linux-fbdev <linux-fbdev@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] fbdev fixes for 3.11
Date: Fri, 09 Aug 2013 10:44:07 +0000	[thread overview]
Message-ID: <5204C7F7.8050503@ti.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]

Hi Linus,

Here are hopefully the last fbdev fixes for 3.11.

 Tomi

The following changes since commit 7808e3291e1e101e9ad6e8263119c4a2abae05ef:

  video: sh7760fb: fix to pass correct device identity to free_irq() (2013-07-29 11:25:03 +0300)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git tags/fbdev-fixes-3.11-rc5

for you to fetch changes up to 70a0f6032985f156bd7e957cfec99c3dd3d592a2:

  ARM: OMAP: dss-common: fix Panda's DVI DDC channel (2013-08-02 15:52:38 +0300)

----------------------------------------------------------------
fbdev fixes:

- omapdss: compilation fix and DVI fix for PandaBoard
- mxsfb: fix colors when using 18bit LCD bus

----------------------------------------------------------------
Hector Palacios (1):
      video: mxsfb: fix color settings for 18bit data bus and 32bpp

Tomi Valkeinen (2):
      OMAPDSS: analog-tv-connector: compile fix
      ARM: OMAP: dss-common: fix Panda's DVI DDC channel

 arch/arm/mach-omap2/dss-common.c                   |  2 +-
 drivers/video/mxsfb.c                              | 26 ----------------------
 .../video/omap2/displays-new/connector-analog-tv.c | 18 +++++++++++++--
 3 files changed, 17 insertions(+), 29 deletions(-)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

                 reply	other threads:[~2013-08-09 10:44 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=5204C7F7.8050503@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --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).