All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH]: ip6_tables: Fixes explanation of valid upper protocol number
Date: Sat, 26 May 2007 15:44:05 +0200	[thread overview]
Message-ID: <465839A5.7080805@trash.net> (raw)
In-Reply-To: <200705250810.l4P8A2DL002869@toshiba.co.jp>

Yasuyuki KOZAKAI wrote:
> This explains the allowed upper protocol numbers. IP6T_F_NOPROTO was
> introduced to use 0 as Hop-by-Hop option header, not wildcard. But that
> seemed to be forgotten. 0 has been used as wildcard since 2002-08-23.
> 
> Signed-off-by: Yasuyuki Kozakai <yasuyuki@netfilter.org>

Queued for 2.6.23, thanks Yasuyuki.

       reply	other threads:[~2007-05-26 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705250810.l4P8A2DL002869@toshiba.co.jp>
2007-05-26 13:44 ` Patrick McHardy [this message]
2007-05-25  8:10 [PATCH]: ip6_tables: Fixes explanation of valid upper protocol number Yasuyuki KOZAKAI

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=465839A5.7080805@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=yasuyuki.kozakai@toshiba.co.jp \
    /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.