From: Pablo Neira Ayuso <pablo@eurodev.net>
To: Marcus Sundberg <marcus@ingate.com>
Cc: Harald Welte <laforge@netfilter.org>,
netfilter-devel@lists.netfilter.org,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH] ctnetlink: Make expect events work
Date: Fri, 13 Jan 2006 01:20:38 +0100 [thread overview]
Message-ID: <43C6F256.7040306@eurodev.net> (raw)
In-Reply-To: <43C6A946.5070009@ingate.com>
Marcus Sundberg wrote:
> expectation events are improperly tagged in the current ctnetlink
> code, this patch makes them work.
Please, be more accurate with your descriptions. The expectation events
are working just fine since NFNL_SUBSYS_CTNETLINK and
NFNL_SUBSYS_CTNETLINK_EXP messages are handled similarly by
libnetfilter_conntrack.
I agree that it's improperly tagged, so I like the change, but it's not
a fix and it shouldn't go to -stable, it's a cleanup. Thanks!
--
Pablo
next prev parent reply other threads:[~2006-01-13 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 19:08 [PATCH] ctnetlink: Make expect events work Marcus Sundberg
2006-01-12 21:03 ` Patrick McHardy
2006-01-12 21:11 ` Marcus Sundberg
2006-01-13 0:20 ` Pablo Neira Ayuso [this message]
2006-01-13 10:54 ` Marcus Sundberg
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=43C6F256.7040306@eurodev.net \
--to=pablo@eurodev.net \
--cc=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=marcus@ingate.com \
--cc=netfilter-devel@lists.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.