netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: micchie@sfc.wide.ad.jp
Cc: netdev@vger.kernel.org, lksctp-developers@lists.sourceforge.net
Subject: Re: [PATCH net-next-2.6 v2 0/2] sctp: Add Auto-ASCONF support
Date: Thu, 07 Apr 2011 20:33:52 -0700 (PDT)	[thread overview]
Message-ID: <20110407.203352.183049674.davem@davemloft.net> (raw)
In-Reply-To: <BC3A4B88-4312-4371-9209-39666C698F60@sfc.wide.ad.jp>

From: Michio Honda <micchie@sfc.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@sfc.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.

  reply	other threads:[~2011-04-08  3:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07  9:08 [PATCH net-next-2.6 v2 0/2] sctp: Add Auto-ASCONF support Michio Honda
2011-04-08  3:33 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-07  9:02 Michio Honda

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=20110407.203352.183049674.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=lksctp-developers@lists.sourceforge.net \
    --cc=micchie@sfc.wide.ad.jp \
    --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 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).