From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] nf_tables updates for net-next
Date: Mon, 04 Nov 2013 19:49:17 -0500 (EST) [thread overview]
Message-ID: <20131104.194917.2150577204163052524.davem@davemloft.net> (raw)
In-Reply-To: <1383602721-5728-1-git-send-email-pablo@netfilter.org>
From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Mon, 4 Nov 2013 23:05:16 +0100
> This batch contains fives nf_tables patches for your net-next tree,
> they are:
>
> * Fix possible use after free in the module removal path of the
> x_tables compatibility layer, from Dan Carpenter.
>
> * Add filter chain type for the bridge family, from myself.
>
> * Fix Kconfig dependencies of the nf_tables bridge family with
> the core, from myself.
>
> * Fix sparse warnings in nft_nat, from Tomasz Bursztyka.
>
> * Remove duplicated include in the IPv4 family support for nf_tables,
> from Wei Yongjun.
>
> You can pull these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nftables.git master
Also looks fine, pulled, thanks!
prev parent reply other threads:[~2013-11-05 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 22:05 [PATCH 0/5] nf_tables updates for net-next Pablo Neira Ayuso
2013-11-04 22:05 ` [PATCH 1/5] netfilter: bridge: fix nf_tables bridge dependencies with main core Pablo Neira Ayuso
2013-11-04 22:05 ` [PATCH 2/5] netfilter: nft_nat: Fix endianness issue reported by sparse Pablo Neira Ayuso
2013-11-04 22:05 ` [PATCH 3/5] netfilter: bridge: nf_tables: add filter chain type Pablo Neira Ayuso
2013-11-04 22:05 ` [PATCH 4/5] netfilter: nf_tables: remove duplicated include from nf_tables_ipv4.c Pablo Neira Ayuso
2013-11-04 22:05 ` [PATCH 5/5] netfilter: nft_compat: use _safe version of list_for_each Pablo Neira Ayuso
2013-11-05 0:49 ` 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=20131104.194917.2150577204163052524.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).