From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH] fix for nfacct infrastructure in net-next
Date: Sun, 01 Jan 2012 23:42:20 -0500 (EST)
Message-ID: <20120101.234220.1974401426311633045.davem@davemloft.net>
References: <20120101162358.GA21795@1984>
	<20120101.180229.1338519415596129407.davem@davemloft.net>
	<20120102010415.GA23310@1984>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
To: pablo@netfilter.org
Return-path: <netfilter-devel-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([198.137.202.13]:57155 "EHLO
	shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751812Ab2ABEn0 (ORCPT
	<rfc822;netfilter-devel@vger.kernel.org>);
	Sun, 1 Jan 2012 23:43:26 -0500
In-Reply-To: <20120102010415.GA23310@1984>
Sender: netfilter-devel-owner@vger.kernel.org
List-ID: <netfilter-devel.vger.kernel.org>

From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Mon, 2 Jan 2012 02:04:15 +0100

> This is not intended for current 3.2-rc7. This is a fix for something
> that is in your net-next tree (upcoming 3.3).

I think this is the communication problem we had, I thought this
was a netfilter bug fix that was already in net-next that you wanted
me to include in net.

Now that I understand the situation I've pulled the fix into net-next,
thanks.