On Fri, Jun 27, 2014 at 3:51 PM, Tomas Henzl wrote:
> On 06/27/2014 08:09 AM, Viswas G wrote:
>> HI Tomas,
>>
>> This lock is not needed as we are already protecting the tag
>> allocation and freeing with the pm8001_ha->lock. We are always acquiring
>> this lock before calling pm8001_tag_alloc
On 06/27/2014 08:09 AM, Viswas G wrote:
> HI Tomas,
>
> This lock is not needed as we are already protecting the tag allocation and
> freeing with the pm8001_ha->lock. We are always acquiring this lock before
> calling
> pm8001_tag_alloc().
>
> We are allocating and freeing the tag in following
HI Tomas,
This lock is not needed as we are already protecting the tag allocation and
freeing with the pm8001_ha->lock. We are always acquiring this lock before
calling
pm8001_tag_alloc().
We are allocating and freeing the tag in following paths,
1) Request/Response path : This we are protec
3 matches
Mail list logo