From: David Miller <davem@davemloft.net>
To: vladislav.yasevich@hp.com
Cc: Weixing.Shi@windriver.com, yjwei@cn.fujitsu.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH v2] sctp: fix sctp to work with ipv6 source address routing
Date: Mon, 03 May 2010 15:56:22 -0700 (PDT) [thread overview]
Message-ID: <20100503.155622.46319916.davem@davemloft.net> (raw)
In-Reply-To: <1272906432-6237-1-git-send-email-vladislav.yasevich@hp.com>
From: Vlad Yasevich <vladislav.yasevich@hp.com>
Date: Mon, 3 May 2010 13:07:12 -0400
> From: Weixing Shi <Weixing.Shi@windriver.com>
>
> <vlad>
> Ok, updated to be a bit more correct. Only leave the function early if the
> first lookup succeeds.
> </vlad>
This patch looks fine to me.
prev parent reply other threads:[~2010-05-03 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BCE68EE.8020500@cn.fujitsu.com>
2010-05-03 16:50 ` [RFC PATCH] sctp: fix sctp to work with ipv6 source address routing Vlad Yasevich
2010-05-03 16:55 ` Vlad Yasevich
2010-05-03 17:07 ` [RFC PATCH v2] " Vlad Yasevich
2010-05-03 22:56 ` 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=20100503.155622.46319916.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Weixing.Shi@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.com \
--cc=yjwei@cn.fujitsu.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).