From: Harald Welte <laforge@gnumonks.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 v5 2/6] gtp: Implement GTP echo response
Date: Sat, 12 Feb 2022 09:18:20 +0100 [thread overview]
Message-ID: <YgdtTGq9uBu3zCF+@nataraja> (raw)
In-Reply-To: <20220211175504.7854-1-marcin.szycik@linux.intel.com>
On Fri, Feb 11, 2022 at 06:55:04PM +0100, Marcin Szycik wrote:
> Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
Reviewed-By: Harald Welte <laforge@gnumonks.org>
Tested-By: Harald Welte <laforge@gnumonks.org>
--
- Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
next prev parent reply other threads:[~2022-02-12 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 17:54 [PATCH net-next v5 0/6] ice: GTP support in switchdev Marcin Szycik
2022-02-11 17:55 ` [RFC PATCH net-next v5 1/6] gtp: Allow to create GTP device without FDs Marcin Szycik
2022-02-12 8:15 ` Harald Welte
2022-02-11 17:55 ` [RFC PATCH net-next v5 2/6] gtp: Implement GTP echo response Marcin Szycik
2022-02-12 8:18 ` Harald Welte [this message]
2022-02-11 17:55 ` [RFC PATCH net-next v5 3/6] net/sched: Allow flower to match on GTP options Marcin Szycik
2022-02-11 17:55 ` [RFC PATCH net-next v5 4/6] gtp: Add support for checking GTP device type Marcin Szycik
2022-02-12 8:19 ` Harald Welte
2022-02-11 17:55 ` [RFC PATCH net-next v5 5/6] ice: Fix FV offset searching Marcin Szycik
2022-02-11 17:55 ` [RFC PATCH net-next v5 6/6] 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=YgdtTGq9uBu3zCF+@nataraja \
--to=laforge@gnumonks.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;
as well as URLs for NNTP newsgroup(s).