All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 6/6] [PATCH] remove module dependency between ctnetlink and	nf_nat
Date: Mon, 13 Oct 2008 16:11:23 +0200	[thread overview]
Message-ID: <48F3570B.2090209@trash.net> (raw)
In-Reply-To: <48F35647.1010407@netfilter.org>

Pablo Neira Ayuso wrote:
> Pablo Neira Ayuso wrote:
>> Patrick McHardy wrote:
>>> Do you want me to apply the patch as attached to this email, or would
>>> you prefer to rediff it?
>> No, I'll send you a new patchset once you set your tree. This patch also
>> needs to include the nfnl_lock/nfnl_unlock logic.
> 
> Oh, I see, since you want to put this into 2.6.27, I'll see you a patch
> for the NAT issue asap and keep the other in the internal queue.

Great, thanks a lot.

  reply	other threads:[~2008-10-13 14:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 15:21 [PATCH 1/6] [PATCH] use nf_conntrack_get instead of atomic_inc Pablo Neira Ayuso
2008-10-11 15:21 ` [PATCH 2/6] [PATCH] helper load-on-demand support for ctnetlink Pablo Neira Ayuso
2008-10-11 15:22 ` [PATCH 3/6] [PATCH] deliver events for conntracks created via ctnetlink Pablo Neira Ayuso
2008-10-11 15:22 ` [PATCH 4/6] [PATCH] bump the expectation helper name Pablo Neira Ayuso
2008-10-11 15:22 ` [PATCH 5/6] [PATCH] dynamic calculation of event message size for ctnetlink Pablo Neira Ayuso
2008-10-11 15:23 ` [PATCH 6/6] [PATCH] remove module dependency between ctnetlink and nf_nat Pablo Neira Ayuso
2008-10-13 13:50   ` Patrick McHardy
2008-10-13 14:06     ` Pablo Neira Ayuso
2008-10-13 14:08       ` Pablo Neira Ayuso
2008-10-13 14:11         ` Patrick McHardy [this message]
2008-10-13 14:11       ` Patrick McHardy

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=48F3570B.2090209@trash.net \
    --to=kaber@trash.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.