From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: djohnson+linux-kernel@sw.starentnetworks.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lksctp-developers@lists.sourceforge.net,
sakkiped@starentnetworks.com
Subject: Re: [PATCH] IPv6: ipv6_addr_type() doesn't know about RFC4193 addresses
Date: Mon, 30 Jul 2007 17:21:05 -0700 (PDT) [thread overview]
Message-ID: <20070730.172105.35015509.davem@davemloft.net> (raw)
In-Reply-To: <20070726.133452.78498553.yoshfuji@linux-ipv6.org>
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date: Thu, 26 Jul 2007 13:34:52 -0500 (CDT)
> In article <18087.57717.495366.413571@zeus.sw.starentnetworks.com> (at Wed, 25 Jul 2007 19:49:09 -0400), Dave Johnson <djohnson+linux-kernel@sw.starentnetworks.com> says:
>
> > ipv6_addr_type() doesn't check for 'Unique Local IPv6 Unicast
> > Addresses' (RFC4193) and returns IPV6_ADDR_RESERVED for that range.
>
> Acked-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Ok, I've applied Dave's patch.
Dave, although it's customary and fine to use "+foo-list" email
addresses for mailing list subscriptions and discussions, I
ask that you don't add that cookie to your signoff lines in
patch submissions and I've removed it from your's in this patch.
Thanks a lot.
prev parent reply other threads:[~2007-07-31 0:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 23:49 [PATCH] IPv6: ipv6_addr_type() doesn't know about RFC4193 addresses Dave Johnson
2007-07-26 0:12 ` David Miller
2007-07-26 1:11 ` Dave Johnson
2007-07-26 17:59 ` [Lksctp-developers] " Vlad Yasevich
2007-07-26 18:37 ` YOSHIFUJI Hideaki / 吉藤英明
2007-07-26 17:21 ` Simon Arlott
2007-07-26 18:00 ` Dave Johnson
2007-07-26 18:10 ` [Lksctp-developers] " Vlad Yasevich
2007-07-26 18:06 ` Rémi Denis-Courmont
2007-07-26 18:34 ` YOSHIFUJI Hideaki / 吉藤英明
2007-07-31 0:21 ` David Miller [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=20070730.172105.35015509.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=djohnson+linux-kernel@sw.starentnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=sakkiped@starentnetworks.com \
--cc=yoshfuji@linux-ipv6.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).