linux-kernel - Re: [PATCH] slimbus: Linux driver framework for SLIMbus.

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]

Message-ID: <0b49042fd7b1b02788b29ccbe0b9b31a.squirrel@www.codeaurora.org>
Date:	Mon, 4 Jun 2012 03:25:32 -0700 (PDT)
From:	"Sagar Dharia" <sdharia@...eaurora.org>
To:	"Joe Perches" <joe@...ches.com>
Cc:	"Sagar Dharia" <sdharia@...eaurora.org>, davidb@...eaurora.org,
	bryanh@...eaurora.org, ohad@...ery.com, rusty@...tcorp.com.au,
	marc@...stictigers.com, rob@...dley.net, joerg.roedel@....com,
	linux-doc@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
	linux-arm-msm@...r.kernel.org, linus.walleij@...aro.org,
	broonie@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org,
	rob.herring@...xeda.com, trenn@...e.de, grant.likely@...retlab.ca,
	kheitke@...eaurora.org, ak@...ux.intel.com, gclemson@...ience.com,
	gregkh@...uxfoundation.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] slimbus: Linux driver framework for SLIMbus.

> Reallocs should _always_ use a new temporary.
> Otherwise, there will be a memory leak of the
> original pointer memory on failure.
>
Thank you Joe for your comments. I will change the allocs, take care of
the styling based on your comments when I split the patch and resubmit.

Regards
Sagar

Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

--
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/