From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2 nf-next 0/6] netfilter: prepare for skb->nf_bridge removal
Date: Wed, 8 Apr 2015 18:47:27 +0200 [thread overview]
Message-ID: <20150408164727.GA1638@salvia> (raw)
In-Reply-To: <1427977905-9927-1-git-send-email-fw@strlen.de>
On Thu, Apr 02, 2015 at 02:31:39PM +0200, Florian Westphal wrote:
> This series prepares skb->nf_bridge pointer removal.
>
> This is a resend without the ip_fragment changes since
> its not clear to me (yet) how to resolve that.
>
> This also means that this resend doesn't include the skb->nf_bridge
> removal since the 'mtu reduction' in ip_fragment() should
> be made private to bridge netfilter first.
Series applied, thanks Florian.
next prev parent reply other threads:[~2015-04-08 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 12:31 [PATCH v2 nf-next 0/6] netfilter: prepare for skb->nf_bridge removal Florian Westphal
2015-04-02 12:31 ` [PATCH v2 nf-next 1/6] netfilter: bridge: don't use nf_bridge_info data to store mac header Florian Westphal
2015-04-02 12:31 ` [PATCH v2 nf-next 2/6] netfilter: bridge: add helpers for fetching physin/outdev Florian Westphal
2015-04-02 12:31 ` [PATCH v2 nf-next 3/6] netfilter: physdev: use helpers Florian Westphal
2015-04-02 12:31 ` [PATCH v2 nf-next 4/6] netfilter: bridge: add and use nf_bridge_info_get helper Florian Westphal
2015-04-02 12:31 ` [PATCH v2 nf-next 5/6] netfilter: bridge: start splitting mask into public/private chunks Florian Westphal
2015-04-02 12:31 ` [PATCH v2 nf-next 6/6] netfilter: bridge: make BRNF_PKT_TYPE flag a bool Florian Westphal
2015-04-08 16:47 ` Pablo Neira Ayuso [this message]
2015-04-08 17:10 ` [PATCH v2 nf-next 0/6] netfilter: prepare for skb->nf_bridge removal Pablo Neira Ayuso
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=20150408164727.GA1638@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
/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).