-----Original Message----- From: Harald Welte laforge@osmocom.org Sent: piątek, 11 lutego 2022 10:12 To: Marcin Szycik marcin.szycik@linux.intel.com Cc: netdev@vger.kernel.org; michal.swiatkowski@linux.intel.com; Drewek, Wojciech wojciech.drewek@intel.com; davem@davemloft.net; kuba@kernel.org; pablo@netfilter.org; osmocom-net-gprs@lists.osmocom.org Subject: Re: [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs
Hi Harald,
Thanks for triggering CI. Do I see correctly that results for our changes are the same as for master?
Regards, Wojtek
Hi Marcin,
On Wed, Feb 09, 2022 at 07:04:01PM +0100, Marcin Szycik wrote:
On 05-Feb-22 17:34, Harald Welte wrote:
Hi Marcin, Wojciech,
thanks for the revised patch. In general it looks fine to me.
Do you have a public git tree with your patchset applied? I'm asking as we do have automatic testing in place at https://jenkins.osmocom.org/ where I just need to specify a remote git repo andit will build this kernel and run the test suite.
I've created a public fork with our patchset applied, please see [1].
Thanks, I've triggered a build, let's hope it works out. Results should be at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-git/20/ and detailed logs at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-git/20/consol...
The same testsuite executed against master can be seen at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-latest-torval... [the high amount of test cases failing is due to the lack of IPv6 support in the kernel GTP].
Let's hope your forked repo renders identical test results to upstream!
Regards, Harald --
- Harald Welte laforge@osmocom.org http://laforge.gnumonks.org/
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)