Daniel Vetter writes:
> On Sun, Feb 18, 2018 at 11:00:56AM +0100, Christophe LEROY wrote:
>> Le 17/02/2018 à 22:19, Pavel Machek a écrit :
>> >
>> > Fix double ;;'s in code.
>> >
>> > Signed-off-by: Pavel Machek
>>
>> A summary of the files modified on top of the patch would help understand
>>
On Mon, Feb 19, 2018 at 2:33 PM, Pavel Machek wrote:
> On Mon 2018-02-19 16:41:35, Daniel Vetter wrote:
>> On Sun, Feb 18, 2018 at 11:00:56AM +0100, Christophe LEROY wrote:
>> >
>> >
>> > Le 17/02/2018 à 22:19, Pavel Machek a écrit :
>> > >
>> > > Fix double ;;'s in code.
>> > >
>> > > Signed-off-
On Mon 2018-02-19 16:41:35, Daniel Vetter wrote:
> On Sun, Feb 18, 2018 at 11:00:56AM +0100, Christophe LEROY wrote:
> >
> >
> > Le 17/02/2018 à 22:19, Pavel Machek a écrit :
> > >
> > > Fix double ;;'s in code.
> > >
> > > Signed-off-by: Pavel Machek
> >
> > A summary of the files modified o
On Sun, Feb 18, 2018 at 11:00:56AM +0100, Christophe LEROY wrote:
>
>
> Le 17/02/2018 à 22:19, Pavel Machek a écrit :
> >
> > Fix double ;;'s in code.
> >
> > Signed-off-by: Pavel Machek
>
> A summary of the files modified on top of the patch would help understand
> the impact.
>
> A maybe t
Currently GFRC is running regardless state of ARC cores in the SMP cluster.
That means even if ARC cores are halted when doing JTAG debugging GFRC
[our source of wall-time] continues to run giving us unexpected warnings
once we allow ARC cores to run due to some tasks being stuck for too
long.
Sta