[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4bf4a97b-c2c3-51db-9bb1-61e6d433c7ca@gmail.com>
Date: Mon, 2 Jan 2017 13:26:01 +0530
From: Arvind Yadav <arvind.yadav.cs@...il.com>
To: Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc: richard@....at, dwmw2@...radead.org, computersforpeace@...il.com,
marek.vasut@...il.com, cyrille.pitchen@...el.com,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V1] mtd : nand : denali :- No need of devm functions
yes, if Memory is live out side function. Then devm_kzalloc()
approach has the benefit of simplifying the different error paths.
Here, Memory is alive with in function. we are going to free allocate memory
then why we need devm api. In this case Devm will first add this entry to
list and immediately it will remove from list. In this case, It's just a
overhead
for devm api.
-Arvind
On Thursday 29 December 2016 10:54 PM, Boris Brezillon wrote:
> The
> devm_kzalloc() approach has the benefit of simplifying the different
> error paths.
Powered by blists - more mailing lists