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 updates & fixes for v5.19-rc1
Date: Mon, 30 May 2022 21:44:08 +0200	[thread overview]
Message-ID: <YpUeiCcb0ntt7wct@ls3530> (raw)

The following changes since commit 42226c989789d8da4af1de0c31070c96726d990c:

  Linux 5.18-rc7 (2022-05-15 18:08:58 -0700)

are available in the Git repository at:

  http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git tags/for-5.19/fbdev-1

for you to fetch changes up to 79b66128f13f5c22dea03a2197495c4b96ab31f5:

  video: fbdev: omap: Add prototype for hwa742_update_window_async() (2022-05-29 10:20:15 +0200)

----------------------------------------------------------------
fbdev fixes and updates for kernel v5.19-rc1

A buch of small fixes and cleanups, including:

- vesafb: Fix a use-after-free due early fb_info cleanup
- clcdfb: Fix refcount leak in clcdfb_of_vram_setup
- hyperv_fb: Allow resolutions with size > 64 MB for Gen1
- pxa3xx-gcu: release the resources correctly in pxa3xx_gcu_probe/remove()
- omapfb: Prevent compiler warning regarding hwa742_update_window_async()

----------------------------------------------------------------
Helge Deller (1):
      video: fbdev: omap: Add prototype for hwa742_update_window_async()

Javier Martinez Canillas (1):
      video: fbdev: vesafb: Fix a use-after-free due early fb_info cleanup

Miaoqian Lin (1):
      video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup

Minghao Chi (2):
      video: fbdev: omapfb: simplify the return expression of dsi_init_pll_data()
      video: fbdev: omapfb: simplify the return expression of nec_8048_connect()

Saurabh Sengar (1):
      video: fbdev: hyperv_fb: Allow resolutions with size > 64 MB for Gen1

Tom Rix (1):
      video: fbdev: xen: remove setting of 'transp' parameter

Yang Yingliang (1):
      video: fbdev: pxa3xx-gcu: release the resources correctly in pxa3xx_gcu_probe/remove()

pengfuyuan (1):
      video: fbdev: radeon: Fix spelling typo in comment

 drivers/video/fbdev/amba-clcd.c                       |  5 ++++-
 drivers/video/fbdev/hyperv_fb.c                       | 19 +------------------
 drivers/video/fbdev/omap/omapfb.h                     |  4 ++++
 .../omap2/omapfb/displays/panel-nec-nl8048hl11.c      |  7 +------
 drivers/video/fbdev/omap2/omapfb/dss/hdmi_pll.c       |  8 +-------
 drivers/video/fbdev/pxa3xx-gcu.c                      | 12 +++++++-----
 drivers/video/fbdev/vesafb.c                          |  5 +++--
 drivers/video/fbdev/xen-fbfront.c                     |  1 -
 include/video/radeon.h                                |  2 +-
 9 files changed, 22 insertions(+), 41 deletions(-)

             reply	other threads:[~2022-05-30 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 19:44 Helge Deller [this message]
2022-05-30 19:58 ` [GIT PULL] fbdev updates & fixes for v5.19-rc1 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=YpUeiCcb0ntt7wct@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).