[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2e1d692c-5f16-4042-9ae9-423e3991834e@suswa.mountain>
Date: Tue, 1 Jul 2025 17:13:00 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Abdun Nihaal <abdun.nihaal@...il.com>
Cc: andy@...nel.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: Re: [PATCH v4 1/2] Revert "staging: fbtft: fix potential memory leak
in fbtft_framebuffer_alloc()"
On Tue, Jul 01, 2025 at 03:10:22PM +0530, Abdun Nihaal wrote:
> This reverts commit eb2cb7dab60f ("staging: fbtft: fix potential memory
> leak in fbtft_framebuffer_alloc()").
>
> An updated patch has been added as commit 505bffe21233 ("staging:
> fbtft: fix potential memory leak in fbtft_framebuffer_alloc()"),
> and so reverting the old patch.
>
> Signed-off-by: Abdun Nihaal <abdun.nihaal@...il.com>
> ---
This is the wrong approach. The original patch was fine. Just
write the next patches on top of that.
regards,
dan carpenter
Powered by blists - more mailing lists