On Fri, 15 Apr 2016, Jan Sebechlebsky wrote:
On 04/15/2016 02:28 AM, Marton Balint wrote:
On Thu, 14 Apr 2016, Marton Balint wrote:
On Tue, 12 Apr 2016, sebechlebsky...@gmail.com wrote:
From: Jan Sebechlebsky
Calling close_slave in case error is to be
On 04/15/2016 02:28 AM, Marton Balint wrote:
On Thu, 14 Apr 2016, Marton Balint wrote:
On Tue, 12 Apr 2016, sebechlebsky...@gmail.com wrote:
From: Jan Sebechlebsky
Calling close_slave in case error is to be returned from open_slave
will free allocated
On Thu, 14 Apr 2016, Marton Balint wrote:
On Tue, 12 Apr 2016, sebechlebsky...@gmail.com wrote:
From: Jan Sebechlebsky
Calling close_slave in case error is to be returned from open_slave
will free allocated resources.
Since failure can happen before bsfs array
On Tue, 12 Apr 2016, sebechlebsky...@gmail.com wrote:
From: Jan Sebechlebsky
Calling close_slave in case error is to be returned from open_slave
will free allocated resources.
Since failure can happen before bsfs array is initialized,
close_slave must check that
From: Jan Sebechlebsky
Calling close_slave in case error is to be returned from open_slave
will free allocated resources.
Since failure can happen before bsfs array is initialized,
close_slave must check that bsfs is not NULL before accessing
tee_slave->bsfs[i]