From: David Miller <davem@davemloft.net>
To: vyasevich@gmail.com
Cc: dborkman@redhat.com, netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/4] Some SCTP cleanups/improvements
Date: Fri, 14 Jun 2013 15:37:46 -0700 (PDT) [thread overview]
Message-ID: <20130614.153746.1697515927497882181.davem@davemloft.net> (raw)
In-Reply-To: <51BB4C46.2080506@gmail.com>
From: Vlad Yasevich <vyasevich@gmail.com>
Date: Fri, 14 Jun 2013 13:00:54 -0400
> On 06/14/2013 12:24 PM, Daniel Borkmann wrote:
>> v2 -> v3:
>> - Applied feedback from Vlad in first patch, rest is unchanged
>>
>> v1 -> v2:
>> - Applied Neil's feedback, I'll send out the first patch at a later
>> point in time though, have not included it in this set
>> - Add two other patches that appear to be useful from the last
>> couple of days debugging SCTP code
>>
>> Let it run through lksctp-tools and also my recent stress test tool,
>> all looks good.
>
> Looks good.
>
> Acked-by: Vlad Yasevich <vyasevich@gmail.com>
Series applied, thanks.
prev parent reply other threads:[~2013-06-14 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 16:24 [PATCH net-next v3 0/4] Some SCTP cleanups/improvements Daniel Borkmann
2013-06-14 16:24 ` [PATCH net-next v3 1/4] net: sctp: sideeffect: throw BUG if primary_path is NULL Daniel Borkmann
2013-06-14 16:24 ` [PATCH net-next v3 2/4] net: sctp: sctp_sf_do_prm_asoc: do SCTP_CMD_INIT_CHOOSE_TRANSPORT first Daniel Borkmann
2013-06-14 16:24 ` [PATCH net-next v3 3/4] net: sctp: minor: remove variable in sctp_init_sock Daniel Borkmann
2013-06-14 16:24 ` [PATCH net-next v3 4/4] net: sctp: sctp_association_init: put refs in reverse order Daniel Borkmann
2013-06-14 17:00 ` [PATCH net-next v3 0/4] Some SCTP cleanups/improvements Vlad Yasevich
2013-06-14 22:37 ` 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=20130614.153746.1697515927497882181.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vyasevich@gmail.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).