On Fri, 3 May 2019 at 16:07, Amar Tumballi Suryanarayan
wrote:
>
>
> On Fri, May 3, 2019 at 3:17 PM Atin Mukherjee wrote:
>
>>
>>
>> On Fri, 3 May 2019 at 14:59, Xavi Hernandez wrote:
>>
>>> Hi Atin,
>>>
>>> On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee
>>> wrote:
>>>
I'm bit puzzled on
On Fri, May 3, 2019 at 3:17 PM Atin Mukherjee wrote:
>
>
> On Fri, 3 May 2019 at 14:59, Xavi Hernandez wrote:
>
>> Hi Atin,
>>
>> On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee
>> wrote:
>>
>>> I'm bit puzzled on the way coverity is reporting the open defects on GD1
>>> component. As you can se
On Fri, 3 May 2019 at 14:59, Xavi Hernandez wrote:
> Hi Atin,
>
> On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee
> wrote:
>
>> I'm bit puzzled on the way coverity is reporting the open defects on GD1
>> component. As you can see from [1], technically we have 6 open defects and
>> all of the rest
Hi Atin,
On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee wrote:
> I'm bit puzzled on the way coverity is reporting the open defects on GD1
> component. As you can see from [1], technically we have 6 open defects and
> all of the rest are being marked as dismissed. We tried to put some
> additiona
I'm bit puzzled on the way coverity is reporting the open defects on GD1
component. As you can see from [1], technically we have 6 open defects and
all of the rest are being marked as dismissed. We tried to put some
additional annotations in the code through [2] to see if coverity starts
feeling ha