Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Helge Deller <deller@kernel.org>
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 and cleanups for v6.13-rc1
Date: Sun, 24 Nov 2024 18:38:26 +0100	[thread overview]
Message-ID: <Z0NkkihDqEwi3k9Y@carbonx1> (raw)

Hi Linus,

please pull two patches for fbdev for this merge window:
One removes a memory leak in an error path, the other drops unused code.

Thanks,
Helge

----------------------------------------------------------------
The following changes since commit 2d5404caa8c7bb5c4e0435f94b28834ae5456623:

  Linux 6.12-rc7 (2024-11-10 14:19:35 -0800)

are available in the Git repository at:

  http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git tags/fbdev-for-6.13-rc1

for you to fetch changes up to 8d7493133bfd89322349be3daaf39a256e4354ac:

  fbdev: omapfb: Remove some deadcode (2024-11-14 15:30:36 +0100)

----------------------------------------------------------------
fbdev fixes and updates for 6.13-rc1:

- omapfb: Remove unused code (Dr. David Alan Gilbert)
- sh7760fb: Fix memory leak in error path of sh7760fb_alloc_mem()
  (Zhen Lei)

----------------------------------------------------------------
Dr. David Alan Gilbert (1):
      fbdev: omapfb: Remove some deadcode

Zhen Lei (1):
      fbdev: sh7760fb: Fix a possible memory leak in sh7760fb_alloc_mem()

 drivers/video/fbdev/omap2/omapfb/dss/dispc.c | 27 ---------------------------
 drivers/video/fbdev/omap2/omapfb/dss/dss.h   |  3 ---
 drivers/video/fbdev/sh7760fb.c               |  3 +--
 3 files changed, 1 insertion(+), 32 deletions(-)

             reply	other threads:[~2024-11-24 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-24 17:38 Helge Deller [this message]
2024-11-26  1:40 ` [GIT PULL] fbdev fixes and cleanups for v6.13-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=Z0NkkihDqEwi3k9Y@carbonx1 \
    --to=deller@kernel.org \
    --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