netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: pablo@netfilter.org
Cc: netdev@vger.kernel.org, openbsc@lists.osmocom.org
Subject: Re: [PATCH 00/25] [v3] netfilter updates for net-next (upcoming 3.5)
Date: Tue, 08 May 2012 14:51:00 -0400 (EDT)	[thread overview]
Message-ID: <20120508.145100.1375355121119755193.davem@davemloft.net> (raw)
In-Reply-To: <1336502303-1722-1-git-send-email-pablo@netfilter.org>

From: pablo@netfilter.org
Date: Tue,  8 May 2012 20:37:58 +0200

> git://1984.lsi.us.es/net-next master

Pulled, thanks.

      parent reply	other threads:[~2012-05-08 18:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 18:37 [PATCH 00/25] [v3] netfilter updates for net-next (upcoming 3.5) pablo
2012-05-08 18:37 ` [PATCH 01/25] netfilter: nf_ct_ecache: refactor notifier registration pablo
2012-05-08 18:38 ` [PATCH 02/25] netfilter: nf_ct_helper: allow to disable automatic helper assignment pablo
2012-05-08 18:38 ` [PATCH 03/25] netfilter: nf_conntrack: use this_cpu_inc() pablo
2012-05-08 18:38 ` [PATCH 04/25] netfilter: bridge: optionally set indev to vlan pablo
2012-05-08 18:38 ` [PATCH 05/25] ipvs: timeout tables do not need GFP_ATOMIC allocation pablo
2012-05-08 18:38 ` [PATCH 06/25] ipvs: LBLC scheduler does not need GFP_ATOMIC allocation on init pablo
2012-05-08 18:38 ` [PATCH 07/25] ipvs: DH scheduler does not need GFP_ATOMIC allocation pablo
2012-05-08 18:38 ` [PATCH 08/25] ipvs: WRR " pablo
2012-05-08 18:38 ` [PATCH 09/25] ipvs: LBLCR scheduler does not need GFP_ATOMIC allocation on init pablo
2012-05-08 18:38 ` [PATCH 10/25] ipvs: SH scheduler does not need GFP_ATOMIC allocation pablo
2012-05-08 18:38 ` [PATCH 11/25] ipvs: use GFP_KERNEL allocation where possible pablo
2012-05-08 18:38 ` [PATCH 12/25] ipvs: ignore IP_VS_CONN_F_NOOUTPUT in backup server pablo
2012-05-08 18:38 ` [PATCH 13/25] ipvs: remove check for IP_VS_CONN_F_SYNC from ip_vs_bind_dest pablo
2012-05-08 18:38 ` [PATCH 14/25] ipvs: fix ip_vs_try_bind_dest to rebind app and transmitter pablo
2012-05-08 18:38 ` [PATCH 15/25] ipvs: always update some of the flags bits in backup pablo
2012-05-08 18:38 ` [PATCH 16/25] ipvs: wakeup master thread pablo
2012-05-08 18:38 ` [PATCH 17/25] ipvs: reduce sync rate with time thresholds pablo
2012-05-08 18:38 ` [PATCH 18/25] ipvs: add support for sync threads pablo
2012-05-08 18:38 ` [PATCH 19/25] ipvs: optimize the use of flags in ip_vs_bind_dest pablo
2012-05-08 18:38 ` [PATCH 20/25] ipvs: ip_vs_ftp: local functions should not be exposed globally pablo
2012-05-08 18:38 ` [PATCH 21/25] ipvs: ip_vs_proto: " pablo
2012-05-08 18:38 ` [PATCH 22/25] net: export sysctl_[r|w]mem_max symbols needed by ip_vs_sync pablo
2012-05-08 18:38 ` [PATCH 23/25] netfilter: nf_ct_expect: partially implement ctnetlink_change_expect pablo
2012-05-08 18:38 ` [PATCH 24/25] netfilter: nf_conntrack: fix explicit helper attachment and NAT pablo
2012-05-08 18:38 ` [PATCH 25/25] netfilter: remove ip_queue support pablo
2012-05-08 18:51 ` 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=20120508.145100.1375355121119755193.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=openbsc@lists.osmocom.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).