Netdev List
 help / color / mirror / Atom feed
From: Harald Welte <laforge@osmocom.org>
To: Marcin Szycik <marcin.szycik@linux.intel.com>
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
Date: Fri, 11 Feb 2022 10:11:43 +0100	[thread overview]
Message-ID: <YgYoT4UWw0Efq33K@nataraja> (raw)
In-Reply-To: <fd23700b-4269-a615-a73d-10476ffaf82d@linux.intel.com>

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 <laforge@osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

  reply	other threads:[~2022-02-11  9:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 16:37 [RFC PATCH net-next v3 0/5] ice: GTP support in switchdev Marcin Szycik
2022-01-27 16:39 ` [RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs Marcin Szycik
2022-02-05 16:34   ` Harald Welte
2022-02-08 13:30     ` Drewek, Wojciech
2022-02-11  9:04       ` Harald Welte
2022-02-09 18:04     ` Marcin Szycik
2022-02-11  9:11       ` Harald Welte [this message]
2022-02-11 10:05         ` Drewek, Wojciech
2022-02-12 11:02           ` Harald Welte
2022-01-27 16:39 ` [RFC PATCH net-next v3 2/5] gtp: Add support for checking GTP device type Marcin Szycik
2022-01-27 16:39 ` [RFC PATCH net-next v3 3/5] net/sched: Allow flower to match on GTP options Marcin Szycik
2022-01-27 16:39 ` [RFC PATCH net-next v3 4/5] ice: Fix FV offset searching Marcin Szycik
2022-01-27 16:39 ` [RFC PATCH net-next v3 5/5] ice: Support GTP-U and GTP-C offload in switchdev Marcin Szycik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YgYoT4UWw0Efq33K@nataraja \
    --to=laforge@osmocom.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=marcin.szycik@linux.intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=osmocom-net-gprs@lists.osmocom.org \
    --cc=pablo@netfilter.org \
    --cc=wojciech.drewek@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox