linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: [GIT PULL] fbdev fixes for v6.2-rc7
Date: Sun, 5 Feb 2023 10:44:23 +0100	[thread overview]
Message-ID: <Y996d9DJSOK3hT3A@ls3530> (raw)

Hi Linus,

please pull the latest fbdev fixes for 6.2-rc7, which
- fix fbcon to prevent fonts bigger than 32x32 pixels to avoid
  overflows reported by syzbot,
- switch omapfb to use kstrtobool(), and
- switch some fbdev drivers to use the backlight helpers

Thanks,
Helge

-------

The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:

  Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)

are available in the Git repository at:

  http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git tags/fbdev-for-6.2-rc7

for you to fetch changes up to 2b09d5d364986f724f17001ccfe4126b9b43a0be:

  fbcon: Check font dimension limits (2023-02-04 14:29:19 +0100)

----------------------------------------------------------------
fbdev updates for kernel 6.2-rc7:

- Check font size in fbcon, reported by UBSAN and syzbot
- Use backlight helpers in various fbdev drivers

----------------------------------------------------------------
Christophe JAILLET (1):
      fbdev: omapfb: Use kstrtobool() instead of strtobool()

Randy Dunlap (1):
      fbdev: fbmon: fix function name in kernel-doc

Samuel Thibault (1):
      fbcon: Check font dimension limits

Stephen Kitt (8):
      fbdev: aty128fb: Use backlight helper
      fbdev: atyfb: Use backlight helper
      fbdev: radeon: Use backlight helper
      fbdev: mx3fb: Use backlight helper
      fbdev: nvidia: Use backlight helper
      fbdev: omapfb: panel-dsi-cm: Use backlight helper
      fbdev: riva: Use backlight helper
      fbdev: atmel_lcdfb: Rework backlight status updates

 drivers/video/fbdev/atmel_lcdfb.c                  | 22 +---------------------
 drivers/video/fbdev/aty/aty128fb.c                 |  6 ++----
 drivers/video/fbdev/aty/atyfb_base.c               |  8 +-------
 drivers/video/fbdev/aty/radeon_backlight.c         |  6 +-----
 drivers/video/fbdev/core/fbcon.c                   |  7 +++++--
 drivers/video/fbdev/core/fbmon.c                   |  2 +-
 drivers/video/fbdev/mx3fb.c                        |  7 +------
 drivers/video/fbdev/nvidia/nv_backlight.c          |  8 +-------
 .../fbdev/omap2/omapfb/displays/panel-dsi-cm.c     |  8 +-------
 .../video/fbdev/omap2/omapfb/dss/display-sysfs.c   |  7 ++++---
 .../video/fbdev/omap2/omapfb/dss/manager-sysfs.c   |  7 ++++---
 .../video/fbdev/omap2/omapfb/dss/overlay-sysfs.c   |  3 ++-
 drivers/video/fbdev/omap2/omapfb/omapfb-sysfs.c    |  3 ++-
 drivers/video/fbdev/riva/fbdev.c                   |  8 +-------
 14 files changed, 27 insertions(+), 75 deletions(-)

             reply	other threads:[~2023-02-05  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05  9:44 Helge Deller [this message]
2023-02-05 19:48 ` [GIT PULL] fbdev fixes for v6.2-rc7 pr-tracker-bot

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=Y996d9DJSOK3hT3A@ls3530 \
    --to=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --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).