From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 80DDFC433EF for ; Fri, 11 Feb 2022 09:20:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348506AbiBKJUS (ORCPT ); Fri, 11 Feb 2022 04:20:18 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:32978 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348572AbiBKJUN (ORCPT ); Fri, 11 Feb 2022 04:20:13 -0500 Received: from ganesha.gnumonks.org (ganesha.gnumonks.org [IPv6:2001:780:45:1d:225:90ff:fe52:c662]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DAA65102A for ; Fri, 11 Feb 2022 01:20:11 -0800 (PST) Received: from uucp by ganesha.gnumonks.org with local-bsmtp (Exim 4.94.2) (envelope-from ) id 1nIS60-00GkoZ-MB; Fri, 11 Feb 2022 10:20:04 +0100 Received: from laforge by localhost.localdomain with local (Exim 4.95) (envelope-from ) id 1nIRxv-004xg7-Qx; Fri, 11 Feb 2022 10:11:43 +0100 Date: Fri, 11 Feb 2022 10:11:43 +0100 From: Harald Welte To: Marcin Szycik Cc: netdev@vger.kernel.org, michal.swiatkowski@linux.intel.com, 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 Message-ID: References: <20220127163749.374283-1-marcin.szycik@linux.intel.com> <20220127163900.374645-1-marcin.szycik@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 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/console The same testsuite executed against master can be seen at https://jenkins.osmocom.org/jenkins/job/ttcn3-ggsn-test-kernel-latest-torvalds/ [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 http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)