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.3
Date: Mon, 07 Sep 2015 12:19:12 +0000	[thread overview]
Message-ID: <55ED80C0.4020800@ti.com> (raw)

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

Hi Linus,

Please pull fbdev changes for 4.3. Not much this time.


The following changes since commit 2c6625cd545bdd66acff14f3394865d43920a5c7:

  Linux 4.2-rc7 (2015-08-16 16:34:13 -0700)

are available in the git repository at:

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

for you to fetch changes up to 57817e619a215588739f3f644986c78b586b541b:

  video: fbdev: atmel_lcdfb: remove useless include (2015-09-02 14:24:51 +0300)

----------------------------------------------------------------
fbdev changes for 4.3

* Minor fixes and cleanups

----------------------------------------------------------------
Alexandre Belloni (1):
      video: fbdev: atmel_lcdfb: remove useless include

Alexey Klimov (1):
      fbdev: udlfb: remove unneeded initialization in few places

Dan Carpenter (1):
      fbdev: fix snprintf() limit in show_bl_curve()

Geert Uytterhoeven (1):
      fbdev: Allow compile test of GPIO consumers if !GPIOLIB

Julia Lawall (1):
      fbdev: ssd1307fb: fix error return code

Krzysztof Kozlowski (3):
      video: fbdev: Drop owner assignment from i2c_driver
      video: fbdev: Drop owner assignment from platform_driver
      video: fbdev: s3c-fb: Constify platform_device_id

Marcin Chojnacki (1):
      fbdev: remove unnecessary memset in vfb

Nicolai Stange (1):
      framebuffer: disable vgacon on microblaze arch

Tomi Valkeinen (2):
      fbdev: fix cea_modes array size
      video: fbdev: atmel: fix warning for const return value

Vaishali Thakkar (1):
      video: fbdev: pxa168fb: Use devm_clk_get

 drivers/video/console/Kconfig                           |  2 +-
 drivers/video/fbdev/Kconfig                             |  2 +-
 drivers/video/fbdev/atmel_lcdfb.c                       |  3 +--
 drivers/video/fbdev/core/fbmon.c                        |  4 ++--
 drivers/video/fbdev/core/fbsysfs.c                      |  2 +-
 drivers/video/fbdev/core/modedb.c                       |  2 +-
 drivers/video/fbdev/omap2/displays-new/encoder-opa362.c |  1 -
 drivers/video/fbdev/pxa168fb.c                          | 14 ++++----------
 drivers/video/fbdev/s3c-fb.c                            |  2 +-
 drivers/video/fbdev/ssd1307fb.c                         |  6 +++---
 drivers/video/fbdev/udlfb.c                             | 10 ++++------
 drivers/video/fbdev/vfb.c                               | 17 ++++++++---------
 include/linux/fb.h                                      |  2 +-
 13 files changed, 28 insertions(+), 39 deletions(-)


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

                 reply	other threads:[~2015-09-07 12:19 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=55ED80C0.4020800@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).