Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-18 Thread Greg Kroah-Hartman
On Tue, Aug 18, 2015 at 01:06:39PM -0400, Raphaël Beamonte wrote: > 2015-08-18 5:15 GMT-04:00 Dan Carpenter : > > To be honest, I have lost track of this patchset. If you are planning > > to redo the other patches can you send it in a new thread? > > Actually, Greg already included the "return

Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-18 Thread Raphaël Beamonte
2015-08-18 5:15 GMT-04:00 Dan Carpenter : > To be honest, I have lost track of this patchset. If you are planning > to redo the other patches can you send it in a new thread? Actually, Greg already included the "return statement" and "DECLARE_WILC_BUFFER" ones. The replacement of printk by

Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-18 Thread Dan Carpenter
To be honest, I have lost track of this patchset. If you are planning to redo the other patches can you send it in a new thread? regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo

Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-18 Thread Raphaël Beamonte
2015-08-18 5:15 GMT-04:00 Dan Carpenter dan.carpen...@oracle.com: To be honest, I have lost track of this patchset. If you are planning to redo the other patches can you send it in a new thread? Actually, Greg already included the return statement and DECLARE_WILC_BUFFER ones. The replacement

Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-18 Thread Greg Kroah-Hartman
On Tue, Aug 18, 2015 at 01:06:39PM -0400, Raphaël Beamonte wrote: 2015-08-18 5:15 GMT-04:00 Dan Carpenter dan.carpen...@oracle.com: To be honest, I have lost track of this patchset. If you are planning to redo the other patches can you send it in a new thread? Actually, Greg already

Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-18 Thread Dan Carpenter
To be honest, I have lost track of this patchset. If you are planning to redo the other patches can you send it in a new thread? regards, dan carpenter -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo

Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-17 Thread Dan Carpenter
On Mon, Aug 17, 2015 at 07:12:47PM -0400, Raphaël Beamonte wrote: > The MALLOC_WILC_BUFFER() macro was using a return statement, and didn't > take care of possible memory leaks and subsequent bugs when it was failing > after succeeding some allocations. This patch corrects this behavior. > >

[PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-17 Thread Raphaël Beamonte
The MALLOC_WILC_BUFFER() macro was using a return statement, and didn't take care of possible memory leaks and subsequent bugs when it was failing after succeeding some allocations. This patch corrects this behavior. Signed-off-by: Raphaël Beamonte ---

Re: [PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-17 Thread Dan Carpenter
On Mon, Aug 17, 2015 at 07:12:47PM -0400, Raphaël Beamonte wrote: The MALLOC_WILC_BUFFER() macro was using a return statement, and didn't take care of possible memory leaks and subsequent bugs when it was failing after succeeding some allocations. This patch corrects this behavior.

[PATCHv3] staging: wilc1000: replace MALLOC_WILC_BUFFER() macro to avoid possible memory leak

2015-08-17 Thread Raphaël Beamonte
The MALLOC_WILC_BUFFER() macro was using a return statement, and didn't take care of possible memory leaks and subsequent bugs when it was failing after succeeding some allocations. This patch corrects this behavior. Signed-off-by: Raphaël Beamonte raphael.beamo...@gmail.com ---