RE: [PATCH] usb: phy: tegra: Using devm API for memory allocation

2012-12-20 Thread Venu Byravarasu
nu Byravarasu > >> Cc: ba...@ti.com; gre...@linuxfoundation.org; linux- > >> ker...@vger.kernel.org; linux-...@vger.kernel.org > >> Subject: Re: [PATCH] usb: phy: tegra: Using devm API for memory > allocation > >> > > > > Stephen, > > As

Re: [PATCH] usb: phy: tegra: Using devm API for memory allocation

2012-12-19 Thread Stephen Warren
t;> ker...@vger.kernel.org; linux-...@vger.kernel.org >> Subject: Re: [PATCH] usb: phy: tegra: Using devm API for memory allocation >> >> On 12/17/2012 11:21 PM, Venu Byravarasu wrote: >>> Using devm_kzalloc for allocating memory needed for PHY >>> pointer and hence remo

RE: [PATCH] usb: phy: tegra: Using devm API for memory allocation

2012-12-18 Thread Venu Byravarasu
ATCH] usb: phy: tegra: Using devm API for memory allocation > > On 12/17/2012 11:21 PM, Venu Byravarasu wrote: > > Using devm_kzalloc for allocating memory needed for PHY > > pointer and hence removing kfree calls to PHY pointer. > > Since the kfree() here used to be in t

Re: [PATCH] usb: phy: tegra: Using devm API for memory allocation

2012-12-18 Thread Stephen Warren
On 12/17/2012 11:21 PM, Venu Byravarasu wrote: > Using devm_kzalloc for allocating memory needed for PHY > pointer and hence removing kfree calls to PHY pointer. Since the kfree() here used to be in tegra_usb_phy_close() rather than any remove() function, does it actually make sense to use devm_kz