From: Harald Welte <laforge@gnumonks.org>
To: Tom Herbert <tom@quantonium.net>
Cc: "David S . Miller" <davem@davemloft.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Andreas Schultz <aschultz@tpip.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Rohit LastName <rohit@quantonium.net>
Subject: Re: [PATCH v7 net-next 00/13] gtp: Additional feature support - Part I
Date: Mon, 13 Nov 2017 05:56:04 +0900 [thread overview]
Message-ID: <20171112205604.hzuttmo3pocg6bju@nataraja> (raw)
In-Reply-To: <20171028164759.5nm7dfpsdqpxewt6@nataraja>
Hi Tom,
sorry for the delayed response. But I remain committed in pushing
the non-controversial part of your GTP patches forward.
On Sat, Oct 28, 2017 at 06:47:59PM +0200, Harald Welte wrote:
> Thanks. As indicated, I'm planning some testing later this weekend on
> the non-IPv6 patches, and am happy to add my Acked-by and/or re-submit
> those to Dave after that.
After some more delays and returning from netdev 2.2, I've finally put
together a testing setup and successfully (manually) tested with the
following patches:
01/13 vxlan: Move gro_cells_init to ndo_init
02/13 iptunnel: Add common functions to get a tunnel route
04/13 gtp: Call common functions to get tunnel routes and add dst_cache
05/13 iptunnel: Generalize tunnel update pmtu
06/13 gtp: Change to use gro_cells
07/13 gtp: Use goto for exceptions in gtp_udp_encap_recv funcs
08/13 gtp: udp recv clean up
09/13 gtp: Call function to update path mtu
10/13 gtp: Eliminate pktinfo and add port configuration
I hereby acknowledge those patches. How should we proceed? Should I
a) do nothing, you will add Acked-By and re-submit?
b) send an individual Acked-By in a reply to each related patch here on
netdev and you will re-submit those patches?
c) simply create a rebased set from those patches and
re-submit them to the list for net-next myself, with the Acked-by?
d) be preposterous and provide a gtp git tree for DaveM to pull from?
As discussed before, I will not merge/ack IPv6 will until we have an
implementation that is interoperable. I have a TODO list of other
bugfixes and improvements for Kernel GTP, but I'm hopeful that IPv6 can
still be addressed before the end of 2017.
Regards,
Harald
--
- 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:[~2017-11-12 21:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 0:09 [PATCH v7 net-next 00/13] gtp: Additional feature support - Part I Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 01/13] vxlan: Move gro_cells_init to ndo_init Tom Herbert
2017-10-28 0:58 ` Eric Dumazet
2017-10-28 0:09 ` [PATCH v7 net-next 02/13] iptunnel: Add common functions to get a tunnel route Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 03/13] vxlan: Call common functions to get tunnel routes Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 04/13] gtp: Call common functions to get tunnel routes and add dst_cache Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 05/13] iptunnel: Generalize tunnel update pmtu Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 06/13] gtp: Change to use gro_cells Tom Herbert
2017-10-28 1:00 ` Eric Dumazet
2017-10-28 0:09 ` [PATCH v7 net-next 07/13] gtp: Use goto for exceptions in gtp_udp_encap_recv funcs Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 08/13] gtp: udp recv clean up Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 09/13] gtp: Call function to update path mtu Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 10/13] gtp: Eliminate pktinfo and add port configuration Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 11/13] gtp: Experimental encapsulation of IPv6 packets Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 12/13] gtp: Experimental support encpasulating over IPv6 Tom Herbert
2017-10-28 0:09 ` [PATCH v7 net-next 13/13] gtp: Allow configuring GTP interface as standalone Tom Herbert
2017-10-28 8:09 ` [PATCH v7 net-next 00/13] gtp: Additional feature support - Part I Harald Welte
2017-10-28 16:16 ` Tom Herbert
2017-10-28 16:47 ` Harald Welte
2017-10-28 18:37 ` Tom Herbert
2017-10-29 1:49 ` David Miller
2017-11-12 20:56 ` Harald Welte [this message]
2017-11-13 0:25 ` Tom Herbert
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=20171112205604.hzuttmo3pocg6bju@nataraja \
--to=laforge@gnumonks.org \
--cc=aschultz@tpip.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=rohit@quantonium.net \
--cc=tom@quantonium.net \
/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