From: David Miller <davem@davemloft.net>
To: micchie@sfc.wide.ad.jp
Cc: yjwei@cn.fujitsu.com, netdev@vger.kernel.org,
lksctp-developers@lists.sourceforge.net
Subject: Re: [PATCH net-next-2.6] sctp: Add Auto-ASCONF support
Date: Mon, 28 Mar 2011 16:18:57 -0700 (PDT) [thread overview]
Message-ID: <20110328.161857.193719177.davem@davemloft.net> (raw)
In-Reply-To: <6DE94EB5-FD33-4829-AE34-C14CFDD5E527@sfc.wide.ad.jp>
From: Michio Honda <micchie@sfc.wide.ad.jp>
Date: Tue, 29 Mar 2011 03:41:34 +0900
> Thanks for the comment, I implemented the setsockopt-based control,
> and ran the checkpatch.pl. I attach the patch.
When posting a new version of a patch, post it as a completely
new posting so that the commit message and other elements are
understood by automated tools properly.
prev parent reply other threads:[~2011-03-28 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 4:34 [PATCH net-next-2.6] sctp: Add Auto-ASCONF support Michio Honda
2011-03-28 5:30 ` Wei Yongjun
2011-03-28 18:41 ` Michio Honda
2011-03-28 23:18 ` 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=20110328.161857.193719177.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=micchie@sfc.wide.ad.jp \
--cc=netdev@vger.kernel.org \
--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).