From: David Miller <davem@davemloft.net>
To: brian.haley@hp.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] inetpeer: Support ipv6 addresses.
Date: Mon, 29 Nov 2010 19:18:46 -0800 (PST) [thread overview]
Message-ID: <20101129.191846.71126590.davem@davemloft.net> (raw)
In-Reply-To: <4CF45D6B.2070007@hp.com>
From: Brian Haley <brian.haley@hp.com>
Date: Mon, 29 Nov 2010 21:11:55 -0500
> On 11/29/2010 04:44 PM, David Miller wrote:
>> + case AF_INET6:
>> + if (!ipv6_addr_cmp((struct in6_addr *)a,
>> + (struct in6_addr *)b))
>> + return true;
>> + break;
>
> ipv6_addr_equal() ?
Yep, makes sense to me.
next prev parent reply other threads:[~2010-11-30 3:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 21:44 [PATCH 1/3] inetpeer: Support ipv6 addresses David Miller
2010-11-29 22:33 ` Stephen Hemminger
2010-11-30 3:18 ` David Miller
2010-11-30 2:11 ` Brian Haley
2010-11-30 3:18 ` David Miller [this message]
2010-11-30 2:33 ` Changli Gao
2010-11-30 3:14 ` David Miller
2010-11-30 4:51 ` Changli Gao
2010-11-30 5:22 ` David Miller
2010-11-30 5:42 ` Eric Dumazet
2010-11-30 5:53 ` David Miller
2010-11-30 6:11 ` Eric Dumazet
2010-11-30 6:31 ` David Miller
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=20101129.191846.71126590.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brian.haley@hp.com \
--cc=netdev@vger.kernel.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).