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: linux-fbdev <linux-fbdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] fbdev changes for 4.7
Date: Fri, 20 May 2016 08:21:03 +0000	[thread overview]
Message-ID: <573EC8EF.2090909@ti.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2593 bytes --]

Hi Linus,

Please pull the fbdev changes for v4.7.

 Tomi

The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9:

  Linux 4.6-rc4 (2016-04-17 19:13:32 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git tags/fbdev-4.7

for you to fetch changes up to ab366b40b8513e7590858229ecbb5e1434a52b54:

  fbdev: Use IS_ENABLED() instead of checking for built-in or module (2016-05-13 15:14:38 +0300)

----------------------------------------------------------------
fbdev changes for 4.7

* imxfb: fix lcd power up
* small fixes and cleanups

----------------------------------------------------------------
Alexey Khoroshilov (1):
      fbdev: fbmem: implement error handling in fbmem_init()

Andy Lutomirski (1):
      efifb: Don't show the mapping VA

Eric Engestrom (1):
      Documentation: fb: fix spelling mistakes

Javier Martinez Canillas (1):
      fbdev: Use IS_ENABLED() instead of checking for built-in or module

Julian Scheel (1):
      fbdev: ssd1307fb: Fix charge pump setting

Peter Ujfalusi (1):
      video: fbdev: omap2: Remove deprecated regulator_can_change_voltage() usage

Simon Horman (1):
      fbdev: sh_mipi_dsi: remove driver

Uwe Kleine-König (2):
      video: fbdev: imxfb: fix semantic of .get_power and .set_power
      video: fbdev: imxfb: add some error handling

Wang Hongcheng (1):
      video: AMBA CLCD: Remove unncessary include in amba-clcd.c

 Documentation/fb/udlfb.txt                   |   6 +-
 drivers/video/Kconfig                        |   4 -
 drivers/video/fbdev/Kconfig                  |   1 -
 drivers/video/fbdev/Makefile                 |   1 -
 drivers/video/fbdev/amba-clcd.c              |   2 -
 drivers/video/fbdev/core/fbmem.c             |  20 +-
 drivers/video/fbdev/efifb.c                  |   6 +-
 drivers/video/fbdev/imxfb.c                  |  44 +-
 drivers/video/fbdev/omap2/omapfb/dss/dsi.c   |  12 +-
 drivers/video/fbdev/omap2/omapfb/dss/hdmi4.c |  12 +-
 drivers/video/fbdev/omap2/omapfb/dss/hdmi5.c |  12 +-
 drivers/video/fbdev/sh_mipi_dsi.c            | 587 ---------------------------
 drivers/video/fbdev/ssd1307fb.c              |   2 +-
 drivers/video/fbdev/via/accel.c              |   2 +-
 drivers/video/fbdev/via/via-core.c           |   4 +-
 include/video/sh_mipi_dsi.h                  |  59 ---
 16 files changed, 73 insertions(+), 701 deletions(-)
 delete mode 100644 drivers/video/fbdev/sh_mipi_dsi.c
 delete mode 100644 include/video/sh_mipi_dsi.h


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

                 reply	other threads:[~2016-05-20  8:21 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=573EC8EF.2090909@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@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).