[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20110407.203352.183049674.davem@davemloft.net>
Date: Thu, 07 Apr 2011 20:33:52 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: micchie@....wide.ad.jp
Cc: netdev@...r.kernel.org, lksctp-developers@...ts.sourceforge.net
Subject: Re: [PATCH net-next-2.6 v2 0/2] sctp: Add Auto-ASCONF support
From: Michio Honda <micchie@....wide.ad.jp>
Date: Thu, 7 Apr 2011 18:08:15 +0900
> SCTP reconfigure the IP addresses in the association by using ASCONF chunks as mentioned in RFC5061.
> For example, we can start to use the newly configured IP address in the existing association.
> ASCONF operation is invoked in two ways:
> First is done by the application to call sctp_bindx() system call.
> Second is automatic operation in the SCTP stack with address events in the host computer (called auto_asconf) .
> The former is already implemented, but the latter is not yet. This patch enables it with one sysctl parameter and setsockopt() system call.
> (This patch is a part of larger patch that supports complete auto_asconf)
>
> Signed-off-by: Michio Honda <micchie@....wide.ad.jp>
This is a very confusing patch submission.
The "0/N" posting should not itself contain a patch, it should merely be
a posting that provides only a top-level description of the patches
that appear in subsequent "1/N", "2/N", etc. postings.
I'm not even going to try and figure out how these patches are really
supposed to be ordered or be applied, and instead ask you to resubmit
this properly.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists