[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191005184035.GA2062613@kroah.com>
Date: Sat, 5 Oct 2019 20:40:35 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Markus Elfring <Markus.Elfring@....de>
Cc: Navid Emamdoost <navid.emamdoost@...il.com>,
devel@...verdev.osuosl.org, kernel-janitors@...r.kernel.org,
Malcolm Priestley <tvboxspy@...il.com>,
Kangjie Lu <kjlu@....edu>, linux-kernel@...r.kernel.org,
Madhumitha Prabakaran <madhumithabiw@...il.com>,
Luis Chamberlain <mcgrof@...nel.org>,
Navid Emamdoost <emamd001@....edu>,
Forest Bond <forest@...ttletooquiet.net>,
Stephen McCamant <smccaman@....edu>
Subject: Re: [PATCH] staging: vt6655: Fix memory leak in vt6655_probe
On Sat, Oct 05, 2019 at 06:30:13PM +0200, Markus Elfring wrote:
> > In vt6655_probe, if vnt_init() fails the cleanup code needs to be called
> > like other error handling cases. The call to device_free_info() is
> > added.
>
> Please improve this change description.
It is fine as-is, please do not confuse people.
Powered by blists - more mailing lists