Hi, Thank you for information.
BR, Duckjung Kim -----Original Message----- From: Richard Cochran [mailto:richardcoch...@gmail.com] Sent: Friday, January 26, 2018 3:06 PM To: Duckjung Kim <duckjung....@ericsson.com> Cc: Linuxptp-devel@lists.sourceforge.net Subject: Re: [Linuxptp-devel] How to prove if my changed codes work well? On Fri, Jan 26, 2018 at 05:43:23AM +0000, Duckjung Kim wrote: > If I change some parts of linuxptp, I will verify it in my own way or system. > But I wonder if it is enough to request a review. So I ask you questions as > below: > > > 1. Is there any procedure that I should prove if my changed codes work > well? > > A. ex1) A new patch should pass some static or dynamic analysis. > > B. ex2) ptp4l should run some test cases(clock creation, clock destroy, > port add, port remove and etc.) successfully. Here are some points to test: - compiles without warnings - passes checkpatch.pl - passes linuxptp-testsuite git://github.com/mlichvar/linuxptp-testsuite.git - ptp4l runs under valgrind without leaks Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
