All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: Shan Wei <shanwei@cn.fujitsu.com>
Cc: David Miller <davem@davemloft.net>,
	Vlad Yasevich <vladislav.yasevich@hp.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	lksctp <linux-sctp@vger.kernel.org>
Subject: Re: [PATCH net-next-2.6 0/3] new SCTP sockets APIs
Date: Mon, 18 Apr 2011 04:07:33 +0000	[thread overview]
Message-ID: <4DABB905.70902@cn.fujitsu.com> (raw)
In-Reply-To: <4DABB43B.9010204@cn.fujitsu.com>


> To David, Vlad:
>
>    There are many patches in vlad's net-next(1*) tree besides these three ones.
>    Maybe vlad is busy doing other things, Should we need to respin these patches
>    base on latest kernel and submit to you? So we can do further work against latest kernel.   
>
>    1*: vlad's net-next tree:
>       http://git.kernel.org/?p=linux/kernel/git/vxy/lksctp-dev.git;a=shortlog;h=refs/heads/net-next

If Vlad is allowed, I can help him to push all of those patchs(or part of them) to
net-next-2.6 tree by many small patchsets.
most of those patch have been waited for about one year.

>
> Wei Yongjun wrote, at 04/18/2011 11:24 AM:
>> This patchset implement some new sockets APIs for net-next-2.6.
>>
>> Wei Yongjun (3):
>>   sctp: implement socket option SCTP_GET_ASSOC_ID_LIST
>>   sctp: change auth event type name to SCTP_AUTHENTICATION_EVENT
>>   sctp: implement event notification SCTP_SENDER_DRY_EVENT
>>
>>  include/net/sctp/sm.h       |    1 +
>>  include/net/sctp/ulpevent.h |    3 ++
>>  include/net/sctp/user.h     |   33 ++++++++++++++++++++++++++-
>>  net/sctp/sm_statefuns.c     |   24 +++++++++++++++++++
>>  net/sctp/sm_statetable.c    |    2 +-
>>  net/sctp/socket.c           |   52 +++++++++++++++++++++++++++++++++++++++++++
>>  net/sctp/ulpevent.c         |   30 ++++++++++++++++++++++++-
>>  7 files changed, 142 insertions(+), 3 deletions(-)
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>

WARNING: multiple messages have this Message-ID (diff)
From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: Shan Wei <shanwei@cn.fujitsu.com>
Cc: David Miller <davem@davemloft.net>,
	Vlad Yasevich <vladislav.yasevich@hp.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	lksctp <linux-sctp@vger.kernel.org>
Subject: Re: [PATCH net-next-2.6 0/3] new SCTP sockets APIs
Date: Mon, 18 Apr 2011 12:07:33 +0800	[thread overview]
Message-ID: <4DABB905.70902@cn.fujitsu.com> (raw)
In-Reply-To: <4DABB43B.9010204@cn.fujitsu.com>


> To David, Vlad:
>
>    There are many patches in vlad's net-next(1*) tree besides these three ones.
>    Maybe vlad is busy doing other things, Should we need to respin these patches
>    base on latest kernel and submit to you? So we can do further work against latest kernel.   
>
>    1*: vlad's net-next tree:
>       http://git.kernel.org/?p=linux/kernel/git/vxy/lksctp-dev.git;a=shortlog;h=refs/heads/net-next

If Vlad is allowed, I can help him to push all of those patchs(or part of them) to
net-next-2.6 tree by many small patchsets.
most of those patch have been waited for about one year.

>
> Wei Yongjun wrote, at 04/18/2011 11:24 AM:
>> This patchset implement some new sockets APIs for net-next-2.6.
>>
>> Wei Yongjun (3):
>>   sctp: implement socket option SCTP_GET_ASSOC_ID_LIST
>>   sctp: change auth event type name to SCTP_AUTHENTICATION_EVENT
>>   sctp: implement event notification SCTP_SENDER_DRY_EVENT
>>
>>  include/net/sctp/sm.h       |    1 +
>>  include/net/sctp/ulpevent.h |    3 ++
>>  include/net/sctp/user.h     |   33 ++++++++++++++++++++++++++-
>>  net/sctp/sm_statefuns.c     |   24 +++++++++++++++++++
>>  net/sctp/sm_statetable.c    |    2 +-
>>  net/sctp/socket.c           |   52 +++++++++++++++++++++++++++++++++++++++++++
>>  net/sctp/ulpevent.c         |   30 ++++++++++++++++++++++++-
>>  7 files changed, 142 insertions(+), 3 deletions(-)
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>

  reply	other threads:[~2011-04-18  4:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18  3:24 [PATCH net-next-2.6 0/3] new SCTP sockets APIs Wei Yongjun
2011-04-18  3:24 ` Wei Yongjun
2011-04-18  3:27 ` [PATCH net-next-2.6 1/3] sctp: implement socket option SCTP_GET_ASSOC_ID_LIST Wei Yongjun
2011-04-18  3:27   ` Wei Yongjun
2011-04-18  3:28 ` [PATCH net-next-2.6 2/3] sctp: change auth event type name to SCTP_AUTHENTICATION_EVENT Wei Yongjun
2011-04-18  3:28   ` Wei Yongjun
2011-04-18  3:29 ` [PATCH net-next-2.6 3/3] sctp: implement event notification SCTP_SENDER_DRY_EVENT Wei Yongjun
2011-04-18  3:29   ` Wei Yongjun
2011-04-18  3:47 ` [PATCH net-next-2.6 0/3] new SCTP sockets APIs Shan Wei
2011-04-18  3:47   ` Shan Wei
2011-04-18  4:07   ` Wei Yongjun [this message]
2011-04-18  4:07     ` Wei Yongjun
2011-04-18  4:09     ` David Miller
2011-04-18  4:09       ` David Miller
2011-04-21 17:36 ` David Miller
2011-04-21 17:36   ` David Miller

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=4DABB905.70902@cn.fujitsu.com \
    --to=yjwei@cn.fujitsu.com \
    --cc=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shanwei@cn.fujitsu.com \
    --cc=vladislav.yasevich@hp.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 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.