From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
nikolay@cumulusnetworks.com, roopa@cumulusnetworks.com
Subject: Re: [PATCH net-next,v3 0/9] connection tracking support for bridge
Date: Thu, 30 May 2019 14:21:35 -0700 (PDT) [thread overview]
Message-ID: <20190530.142135.2140457379658447198.davem@davemloft.net> (raw)
In-Reply-To: <20190529112539.2126-1-pablo@netfilter.org>
From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Wed, 29 May 2019 13:25:30 +0200
> This patchset adds native connection tracking support for the bridge.
Series applied.
prev parent reply other threads:[~2019-05-30 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 11:25 [PATCH net-next,v3 0/9] connection tracking support for bridge Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 1/9] net: ipv4: add skbuff fraglist splitter Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 2/9] net: ipv6: " Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 3/9] net: ipv4: split skbuff into fragments transformer Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 4/9] net: ipv6: " Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 5/9] net: ipv4: place control buffer handling away from fragmentation iterators Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 6/9] netfilter: nf_conntrack: allow to register bridge support Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 7/9] netfilter: bridge: add connection tracking system Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 8/9] netfilter: nf_conntrack_bridge: add support for IPv6 Pablo Neira Ayuso
2019-05-29 11:25 ` [PATCH net-next,v3 9/9] netfilter: nf_conntrack_bridge: register inet conntrack for bridge Pablo Neira Ayuso
2019-05-30 21:21 ` David Miller [this message]
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=20190530.142135.2140457379658447198.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=pablo@netfilter.org \
--cc=roopa@cumulusnetworks.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).