linux-kernel - Re: [PATCH v4 1/2] memory: ti-aemif: introduce AEMIF driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Feb 2014 06:34:03 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Ivan Khoronzhuk <ivan.khoronzhuk@...com>
Cc:	santosh.shilimkar@...com, rob@...dley.net, linux@....linux.org.uk,
	galak@...nel.crashing.org, devicetree@...r.kernel.org,
	pawel.moll@....com, mark.rutland@....com, rob.herring@...xeda.com,
	swarren@...dotorg.org, ijc+devicetree@...lion.org.uk,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-mtd@...ts.infradead.org, grygorii.strashko@...com,
	dwmw2@...radead.org, nsekhar@...com,
	"[initial author] Murali Karicheri" <m-karicheri2@...com>
Subject: Re: [PATCH v4 1/2] memory: ti-aemif: introduce AEMIF driver

On Wed, Feb 19, 2014 at 12:32:02PM +0200, Ivan Khoronzhuk wrote:
> >> +	aemif->clk = devm_clk_get(dev, NULL);
> >> +	if (IS_ERR(aemif->clk)) {
> >> +		dev_err(dev, "cannot get clock 'aemif'\n");
> >> +		return PTR_ERR(aemif->clk);
> > No freeing memory?
> 
> There is no need to free memory explicitly.
> devm_kzalloc is used instead of kzalloc.

Yes, but where does the device on the error path get removed?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/