From: Vlad Yasevich <vyasevich@gmail.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATCH v2 net-next 4/5] net: sctp: improve sctp_select_active_and_retran_path selection
Date: Wed, 11 Jun 2014 15:51:37 +0000 [thread overview]
Message-ID: <53987B09.30904@gmail.com> (raw)
In-Reply-To: <539874E3.2010607@redhat.com>
On 06/11/2014 11:25 AM, Daniel Borkmann wrote:
> On 06/11/2014 05:21 PM, Vlad Yasevich wrote:
>> On 06/11/2014 11:03 AM, Daniel Borkmann wrote:
>>> In case we neither found a possible ACTIVE or UNKNOWN trans_pri
>>> resp. trans_sec from our current transport list, we currently
>> ^^^^^^
>>
>> Not sure what you wanted to say here.
>
> Actually just the case of trans_pri = NULL, trans_sec = NULL
> since they weren't updated when traversing the list, sorry if
> this was unclear.
The "resp." seemed like either an abbreviation or an incomplete
word. In either case, it should be clarified.
-vlad
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vyasevich@gmail.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATCH v2 net-next 4/5] net: sctp: improve sctp_select_active_and_retran_path selection
Date: Wed, 11 Jun 2014 11:51:37 -0400 [thread overview]
Message-ID: <53987B09.30904@gmail.com> (raw)
In-Reply-To: <539874E3.2010607@redhat.com>
On 06/11/2014 11:25 AM, Daniel Borkmann wrote:
> On 06/11/2014 05:21 PM, Vlad Yasevich wrote:
>> On 06/11/2014 11:03 AM, Daniel Borkmann wrote:
>>> In case we neither found a possible ACTIVE or UNKNOWN trans_pri
>>> resp. trans_sec from our current transport list, we currently
>> ^^^^^^
>>
>> Not sure what you wanted to say here.
>
> Actually just the case of trans_pri == NULL, trans_sec == NULL
> since they weren't updated when traversing the list, sorry if
> this was unclear.
The "resp." seemed like either an abbreviation or an incomplete
word. In either case, it should be clarified.
-vlad
next prev parent reply other threads:[~2014-06-11 15:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 15:03 [PATCH v2 net-next 0/5] SCTP update Daniel Borkmann
2014-06-11 15:03 ` Daniel Borkmann
2014-06-11 15:03 ` [PATCH v2 net-next 1/5] ktime: add ktime_after and ktime_before helper Daniel Borkmann
2014-06-11 15:03 ` Daniel Borkmann
2014-06-11 15:03 ` [PATCH v2 net-next 2/5] net: sctp: refactor active path selection Daniel Borkmann
2014-06-11 15:03 ` Daniel Borkmann
2014-06-11 15:03 ` [PATCH v2 net-next 3/5] net: sctp: migrate most recently used transport to ktime Daniel Borkmann
2014-06-11 15:03 ` Daniel Borkmann
2014-06-11 15:03 ` [PATCH v2 net-next 4/5] net: sctp: improve sctp_select_active_and_retran_path selection Daniel Borkmann
2014-06-11 15:03 ` Daniel Borkmann
2014-06-11 15:21 ` Vlad Yasevich
2014-06-11 15:21 ` Vlad Yasevich
2014-06-11 15:25 ` Daniel Borkmann
2014-06-11 15:25 ` Daniel Borkmann
2014-06-11 15:51 ` Vlad Yasevich [this message]
2014-06-11 15:51 ` Vlad Yasevich
2014-06-11 15:52 ` Daniel Borkmann
2014-06-11 15:52 ` Daniel Borkmann
2014-06-11 15:03 ` [PATCH v2 net-next 5/5] net: sctp: fix incorrect type in gfp initializer Daniel Borkmann
2014-06-11 15:03 ` Daniel Borkmann
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=53987B09.30904@gmail.com \
--to=vyasevich@gmail.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=linux-sctp@vger.kernel.org \
--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 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.