From: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
To: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
"David J. Wilder"
<dwilder-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 8/9] ib/addr: simplify resolving IPv4 addresses
Date: Thu, 19 Nov 2009 16:52:42 +0200 [thread overview]
Message-ID: <4B055BBA.8020505@Voltaire.com> (raw)
In-Reply-To: <4B024258.7070500-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
> I reviewed patches 1-6 & 8 and they all look fine, I will give the whole series
> a try later this week to further validate them
I tested the patch series (V2 for the patches that have it, V1 for the rest) over 2.6.32-rc5
and librdmacm-1.0.8-1.el5 covering AF_INET/PS_TCP unicast and AF_INET/PS_IPOIB multicast and
bonding (operability and address-change event). I used mckey and rping, all worked fine,
thanks for driving this change set, Sean. David, I'll be happy to hear how the IPv6 testing went, lets get this going.
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-19 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 0:07 [PATCH 8/9] ib/addr: simplify resolving IPv4 addresses Sean Hefty
[not found] ` <AD17449F0C4E4FE7B20C32412F077C00-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-11-17 6:27 ` Or Gerlitz
[not found] ` <4B024258.7070500-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-11-17 20:51 ` David J. Wilder
[not found] ` <1258491091.11975.1.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>
2009-11-17 21:26 ` Sean Hefty
2009-11-19 14:52 ` Or Gerlitz [this message]
[not found] ` <4B055BBA.8020505-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-11-19 16:46 ` David J. Wilder
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=4B055BBA.8020505@Voltaire.com \
--to=ogerlitz-hkgkho2ms0fwk0htik3j/w@public.gmane.org \
--cc=dwilder-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 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.