On Mon, Sep 23, 2019 at 02:26:42PM -0700, Ben Pfaff wrote:
> On Fri, Sep 20, 2019 at 09:51:54AM -0700, William Tu wrote:
> > From: Damijan Skvarc
> >
> > While checking valgrind reports after running "make check-valgrind" I have
> > noticed
> > reports for several tests similar to the
On Fri, Sep 20, 2019 at 09:51:54AM -0700, William Tu wrote:
> From: Damijan Skvarc
>
> While checking valgrind reports after running "make check-valgrind" I have
> noticed
> reports for several tests similar to the following:
Thanks. I applied this to master and am working on backports.
Hi Ben,
I'm not the co-author of this patch, I'm just sending for the original author.
Please remove me, thanks
William
On Fri, Sep 20, 2019 at 10:01 AM 0-day Robot wrote:
>
> Bleep bloop. Greetings William Tu, I am a robot and I have tried out your
> patch.
> Thanks for your contribution.
>
>
Bleep bloop. Greetings William Tu, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Unexpected sign-offs from developers who are not authors or co-authors
or committers:
From: Damijan Skvarc
While checking valgrind reports after running "make check-valgrind" I have
noticed
reports for several tests similar to the following:
==5345== Memcheck, a memory error detector
==5345== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==5345== Using
