On Thu, Aug 02, 2012 at 04:41:25PM +0530, Shubhrajyoti D wrote:
The kfree() is taken care of by the spi core (spi_master_release() function)
that is called once the last reference to the underlying struct device has
been released. So the driver need not call kfree.
Applied, thanks.
On Wednesday 01 August 2012 08:37 PM, Guenter Roeck wrote:
On Wed, Aug 01, 2012 at 03:06:28PM +0530, Shubhrajyoti D wrote:
The kfree() is taken care of by the spi core (spi_master_release() function)
that is called once the last reference to the underlying struct device has
been released. So
The kfree() is taken care of by the spi core (spi_master_release() function)
that is called once the last reference to the underlying struct device has
been released. So the driver need not call kfree.
Also the put was missed in some of the error handling fix the same.
There by fixing the missing
On Thu, Aug 02, 2012 at 03:37:13PM +0530, Shubhrajyoti wrote:
On Wednesday 01 August 2012 08:37 PM, Guenter Roeck wrote:
On Wed, Aug 01, 2012 at 03:06:28PM +0530, Shubhrajyoti D wrote:
The kfree() is taken care of by the spi core (spi_master_release()
function)
that is called once the
The kfree() is taken care of by the spi core (spi_master_release() function)
that is called once the last reference to the underlying struct device has
been released. So the driver need not call kfree.
Also the put was missed in some of the error handling fix the same.
There by fixing the missing
On Wed, Aug 01, 2012 at 03:06:28PM +0530, Shubhrajyoti D wrote:
The kfree() is taken care of by the spi core (spi_master_release() function)
that is called once the last reference to the underlying struct device has
been released. So the driver need not call kfree.
Also the put was missed in
