On Fri, Nov 11, 2016 at 02:42:40PM +0200, Leon Romanovsky wrote: > > I have checked the patches and fixed it and send the patchv4. I think that > > the patchv4 will not have errors and warnings for travis CI testing, but > > I don't have the Travis CI environment for testing it. > > I have tried to install the test environment according to your test log and it > > is fail. > > In addtion that, I have tested it for patchv1/patchv2/patch3 by use the following way and it > > is ok > > 1. directly use the default script file build.sh > > ./build.sh > > 2. use CC=aarch64-linux-gnu-gcc build > > mkdir build > > cd build > > CC=aarch64-linux-gnu-gcc cmake -Gninja -DENABLE_RESOLVE_NEIGH=0 .. For the 32 bit bugs all you need to do is run on x86 with the 32 bit compiler support installed: $ CFLAGS=-m32 cmake -GNinja .. $ ninja > 4. Send pull request to rdma-core via github interface and it will check > automatically. This is certainly a better option than having Leon test your patches, just keep force pushing to your own pull request until travis is happy. Make sure the 32 bit problems are fixed properly, use inttypes.h, uintptr, and so forth. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
