netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Masahide Nakamura <nakam@linux-ipv6.org>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: [PATCH] [iproute2] XFRM: support ICMP/ICMPv6's type and code
Date: Tue, 28 Sep 2004 11:46:37 -0700	[thread overview]
Message-ID: <1096397197.21799.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20040906164742.54795bf4@localhost>

On Mon, 2004-09-06 at 16:47 +0900, Masahide Nakamura wrote:
> This patch supports ICMP/ICMPv6's type and code in IPsec
> selector. Kernel has supported this feature from 2.6.9-rc1.

The set of XFRM related patches are in the latest version due this week.


      reply	other threads:[~2004-09-28 18:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-06  7:47 [PATCH] [iproute2] XFRM: support ICMP/ICMPv6's type and code Masahide Nakamura
2004-09-28 18:46 ` Stephen Hemminger [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=1096397197.21799.17.camel@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=linux-net@vger.kernel.org \
    --cc=nakam@linux-ipv6.org \
    --cc=netdev@oss.sgi.com \
    /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).