From: Pablo Neira Ayuso <pablo@netfilter.org>
To: kaber@trash.net
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 3/3] ctnetlink: optional reliable conntrack event delivery
Date: Mon, 30 Mar 2009 15:32:40 +0200 [thread overview]
Message-ID: <49D0C9F8.2030005@netfilter.org> (raw)
In-Reply-To: <20090330132840.14337.57303.stgit@Decadence>
Pablo Neira Ayuso wrote:
> This patch does not include the removal of the notify chain as
> Patrick suggested yet, but I'll work on such change on top of this
> patch if this is OK.
^^^
BTW, this is comment is obsolte. I wrote it and then go back to add the
notify chain removal as the very first patch :).
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2009-03-30 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 13:27 [PATCH 0/3] [RFC] conntrack event caching changes Pablo Neira Ayuso
2009-03-30 13:27 ` [PATCH 1/3] netfilter: ecache: replace notify chain by function pointer Pablo Neira Ayuso
2009-03-30 13:28 ` [PATCH 2/3] conntrack: ecache: move event cache to conntrack extension infrastructure Pablo Neira Ayuso
2009-03-30 13:28 ` [PATCH 3/3] ctnetlink: optional reliable conntrack event delivery Pablo Neira Ayuso
2009-03-30 13:32 ` Pablo Neira Ayuso [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=49D0C9F8.2030005@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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.