[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1751086324.git.abdun.nihaal@gmail.com>
Date: Sat, 28 Jun 2025 10:29:05 +0530
From: Abdun Nihaal <abdun.nihaal@...il.com>
To: andy@...nel.org
Cc: Abdun Nihaal <abdun.nihaal@...il.com>,
dan.carpenter@...aro.org,
gregkh@...uxfoundation.org,
lorenzo.stoakes@...cle.com,
tzimmermann@...e.de,
riyandhiman14@...il.com,
willy@...radead.org,
notro@...nnes.org,
thomas.petazzoni@...e-electrons.com,
dri-devel@...ts.freedesktop.org,
linux-fbdev@...r.kernel.org,
linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] staging: fbtft: cleanup fbtft_framebuffer_alloc()
v2:
- Change the earlier patch to also handle the error code returned by
fb_deferred_io_init() and update Fixes tag to point to the commit that
introduced the memory allocation (which leads to leak).
- Add second patch to make the error handling order symmetric to
fbtft_framebuffer_release() and also remove managed allocation for
txbuf as suggested by Andy and Dan.
Link to v1: https://lore.kernel.org/all/20250626172412.18355-1-abdun.nihaal@gmail.com/
Abdun Nihaal (2):
staging: fbtft: fix potential memory leak in fbtft_framebuffer_alloc()
staging: fbtft: cleanup error handling in fbtft_framebuffer_alloc()
drivers/staging/fbtft/fbtft-core.c | 39 +++++++++++++++++-------------
1 file changed, 22 insertions(+), 17 deletions(-)
--
2.43.0
Powered by blists - more mailing lists