The Ethernet initialization functions are supposed to return the number of
devices initialized, so fix tsec_eth_init() so that it returns the number of
TSECs initialized instead of just zero. This is safe because the return value
is currently ignored by all callers, but now they don't have to igno
On Jun 4, 2010, at 3:50 PM, Timur Tabi wrote:
> The Ethernet initialization functions are supposed to return the number of
> devices initialized, so fix tsec_eth_init() so that it returns the number of
> TSECs initialized instead of just zero. This is safe because the return value
> is currently
Andy Fleming wrote:
> The old way continued even if one of the tsecs failed to initialize. Let's
> preserve the original behavior in that sense:
>
> for (i = 0; i < num; i++) {
> ret = tsec_initialize(bis, &tsecs[i]);
> if (ret >= 0)
> count++;
> }
This code has multi
On Jun 4, 2010, at 4:01 PM, Timur Tabi wrote:
> Andy Fleming wrote:
>
>> The old way continued even if one of the tsecs failed to initialize. Let's
>> preserve the original behavior in that sense:
>>
>> for (i = 0; i < num; i++) {
>> ret = tsec_initialize(bis, &tsecs[i]);
>> if (ret
Andy Fleming wrote:
> You just noted that tsec_eth_init should return the number of tsecs
> initialized successfully. Therefore, the callers can check that number,
> and respond accordingly. tsec_initialize() can report the error. If we
> want more elaborate error handling, we can devise somethi
On 6/4/2010 2:42 PM, Timur Tabi wrote:
> Andy Fleming wrote:
>
>> You just noted that tsec_eth_init should return the number of tsecs
>> initialized successfully. Therefore, the callers can check that number,
>> and respond accordingly. tsec_initialize() can report the error. If we
>> want m
6 matches
Mail list logo
