From: "David S. Miller" <davem@davemloft.net>
To: kaber@trash.net
Cc: netdev@vger.kernel.org, netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 00/10]: Netfilter IPsec support
Date: Thu, 10 Nov 2005 21:17:24 -0800 (PST) [thread overview]
Message-ID: <20051110.211724.83727693.davem@davemloft.net> (raw)
In-Reply-To: <43740D9C.80003@trash.net>
From: Patrick McHardy <kaber@trash.net>
Date: Fri, 11 Nov 2005 04:18:52 +0100
> This is the latest set patches for netfilter IPsec support.
> The use of netif_rx for the innermost SA if it used transport
> mode has been replaced by explicit NF_HOOK calls in
> xfrm{4,6}_input.c.
Note that I consider this stuff 2.6.16 material.
We do have a lot of networking changes in 2.6.15
as it is, and also it would be good for these changes
to get some review and discussion time.
next prev parent reply other threads:[~2005-11-11 5:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 3:18 [PATCH 00/10]: Netfilter IPsec support Patrick McHardy
2005-11-11 5:17 ` David S. Miller [this message]
2005-11-11 5:24 ` Patrick McHardy
2005-11-11 10:13 ` Gerd v. Egidy
2005-11-11 12:09 ` Patrick McHardy
2005-11-15 15:50 ` Marco Berizzi
2005-11-17 2:35 ` 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=20051110.211724.83727693.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--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 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).