From: Patrick McHardy <kaber@trash.net>
To: Balazs Scheidler <bazsi@balabit.hu>
Cc: Jan Engelhardt <jengelh@medozas.de>,
netfilter-devel@vger.kernel.org, tproxy@lists.balabit.hu,
Harry Mason <harry.mason@smoothwall.net>
Subject: Re: [PATCH 03/11] TProxy: reuse a 32bit hole in struct ipv6_pinfo
Date: Mon, 31 Aug 2009 14:27:30 +0200 [thread overview]
Message-ID: <4A9BC1B2.6040002@trash.net> (raw)
In-Reply-To: <1251615361.18025.32.camel@bzorp.balabit>
Balazs Scheidler wrote:
> By the way, what should be the proper procedure for posting patches that
> are tproxy specific but touch the core networking code? Should those go
> through Patrick, or should I just post them to netdev? Or just
> cross-post the patch series to both lists?
When further netfilter patches depend on those changes, they should
probably go through me, but you should CC netdev and the maintainers
of the code in question.
next prev parent reply other threads:[~2009-08-31 12:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 14:03 [PATCH 00/11] TProxy for IPv6 Balazs Scheidler
2009-08-15 8:00 ` [PATCH 01/11] TProxy: kick out TIME_WAIT sockets in case a new connection comes in with the same tuple Balazs Scheidler
2009-08-15 12:01 ` [PATCH 02/11] TProxy: add lookup type checks for UDP in nf_tproxy_get_sock_v4() Balazs Scheidler
2009-08-23 9:02 ` [PATCH 03/11] TProxy: reuse a 32bit hole in struct ipv6_pinfo Balazs Scheidler
2009-08-29 16:46 ` Jan Engelhardt
2009-08-30 6:56 ` Balazs Scheidler
2009-08-30 10:49 ` Jan Engelhardt
2009-08-31 12:27 ` Patrick McHardy [this message]
2009-08-23 9:11 ` [PATCH 04/11] TProxy: split off ipv6 defragmentation to a separate module Balazs Scheidler
2009-08-23 9:16 ` [PATCH 05/11] TProxy: added const specifiers to udp lookup functions Balazs Scheidler
2009-08-23 9:19 ` [PATCH 06/11] TProxy: added udp6_lib_lookup function Balazs Scheidler
2009-08-24 12:47 ` [PATCH 07/11] TProxy: implement IPv6 "local" routing type Balazs Scheidler
2009-08-24 12:48 ` [PATCH 08/11] TProxy: allow non-local binds of IPv6 sockets if IP_TRANSPARENT is enabled Balazs Scheidler
2009-08-24 12:51 ` [PATCH 09/11] TProxy: added IPv6 socket lookup function to nf_tproxy_core Balazs Scheidler
2009-08-24 12:51 ` [PATCH 10/11] TProxy: added IPv6 support to the TPROXY target Balazs Scheidler
2009-08-24 12:52 ` [PATCH 11/11] TProxy: added IPv6 support to the socket match Balazs Scheidler
2009-09-04 6:07 ` [PATCH 00/11] TProxy for IPv6 Amos Jeffries
2009-09-04 9:28 ` Jan Engelhardt
2009-09-14 12:20 ` Amos Jeffries
2009-09-14 12:29 ` Jan Engelhardt
2009-09-15 11:58 ` Amos Jeffries
2009-09-08 18:42 ` Balazs Scheidler
2009-09-11 12:12 ` Amos Jeffries
[not found] ` <1252059564.7452.17.camel@nyarlathotep>
[not found] ` <1252435673.32029.45.camel@bzorp.balabit>
2009-09-14 7:41 ` Balazs Scheidler
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=4A9BC1B2.6040002@trash.net \
--to=kaber@trash.net \
--cc=bazsi@balabit.hu \
--cc=harry.mason@smoothwall.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=tproxy@lists.balabit.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.