From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/9] Netfilter/IPVS updates for net-next
Date: Sun, 05 Oct 2014 21:33:09 -0400 (EDT) [thread overview]
Message-ID: <20141005.213309.868146350129561592.davem@davemloft.net> (raw)
In-Reply-To: <1412356824-6362-1-git-send-email-pablo@netfilter.org>
From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Fri, 3 Oct 2014 19:20:15 +0200
> The following patchset contains another batch with Netfilter/IPVS updates
> for net-next, they are:
...
> You can pull these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git
Pulled, thanks a lot Pablo.
prev parent reply other threads:[~2014-10-06 1:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 17:20 [PATCH 0/9] Netfilter/IPVS updates for net-next Pablo Neira Ayuso
2014-10-03 17:20 ` [PATCH 1/9] netfilter: nft_reject: introduce icmp code abstraction for inet and bridge Pablo Neira Ayuso
2014-10-03 17:20 ` [PATCH 2/9] netfilter: move nf_send_resetX() code to nf_reject_ipvX modules Pablo Neira Ayuso
2014-10-07 14:45 ` Eric Dumazet
2014-10-03 17:20 ` [PATCH 3/9] netfilter: use IS_ENABLED(CONFIG_BRIDGE_NETFILTER) Pablo Neira Ayuso
2014-10-03 17:20 ` [PATCH 4/9] netfilter: nf_tables: wait for call_rcu completion on module removal Pablo Neira Ayuso
2014-10-03 17:20 ` [PATCH 5/9] netfilter: nft_compat: remove incomplete 32/64 bits arch compat code Pablo Neira Ayuso
2014-10-03 17:20 ` [PATCH 6/9] netfilter: nf_tables: allow to filter from prerouting and postrouting Pablo Neira Ayuso
2014-10-03 17:20 ` [PATCH 7/9] netfilter: explicit module dependency between br_netfilter and physdev Pablo Neira Ayuso
2014-10-03 17:20 ` [PATCH 8/9] ipvs: Clean up comment style in ip_vs.h Pablo Neira Ayuso
2014-10-03 17:20 ` [PATCH 9/9] netfilter: nft_masq: register/unregister notifiers on module init/exit Pablo Neira Ayuso
2014-10-06 1:33 ` 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=20141005.213309.868146350129561592.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).