From: David Laight <David.Laight@ACULAB.COM>
To: 'Xin Long' <lucien.xin@gmail.com>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>,
"marcelo.leitner@gmail.com" <marcelo.leitner@gmail.com>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>
Subject: RE: [PATCHv3 net-next 0/5] sctp: update from rfc7829
Date: Thu, 17 Oct 2019 09:04:01 +0000 [thread overview]
Message-ID: <a62ea0845f224f15ad42cf9818040919@AcuMS.aculab.com> (raw)
In-Reply-To: <CADvbK_cBaydDVnmcKvUWwsbf+u_GgAumoq7wW7FQtFg_TZNiiw@mail.gmail.com>
From: Xin Long
> Sent: 17 October 2019 05:57
...
> > I'm only an SCTP user, but I think some of the API changes aren't right.
> Hi, David L.
>
> I think you must know quite a few user cases.
>
> Before I repost, can you pls give the exact places where the API
> changes may not be right as you've already done in v1 and v2, so
> that I can correct them.
I'll try to find time to look later today.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
WARNING: multiple messages have this Message-ID (diff)
From: David Laight <David.Laight@ACULAB.COM>
To: 'Xin Long' <lucien.xin@gmail.com>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-sctp@vger.kernel.org" <linux-sctp@vger.kernel.org>,
"marcelo.leitner@gmail.com" <marcelo.leitner@gmail.com>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>
Subject: RE: [PATCHv3 net-next 0/5] sctp: update from rfc7829
Date: Thu, 17 Oct 2019 09:04:01 +0000 [thread overview]
Message-ID: <a62ea0845f224f15ad42cf9818040919@AcuMS.aculab.com> (raw)
In-Reply-To: <CADvbK_cBaydDVnmcKvUWwsbf+u_GgAumoq7wW7FQtFg_TZNiiw@mail.gmail.com>
RnJvbTogWGluIExvbmcNCj4gU2VudDogMTcgT2N0b2JlciAyMDE5IDA1OjU3DQouLi4NCj4gPiBJ
J20gb25seSBhbiBTQ1RQIHVzZXIsIGJ1dCBJIHRoaW5rIHNvbWUgb2YgdGhlIEFQSSBjaGFuZ2Vz
IGFyZW4ndCByaWdodC4NCj4gSGksIERhdmlkIEwuDQo+IA0KPiBJIHRoaW5rIHlvdSBtdXN0IGtu
b3cgcXVpdGUgYSBmZXcgdXNlciBjYXNlcy4NCj4gDQo+IEJlZm9yZSBJIHJlcG9zdCwgY2FuIHlv
dSBwbHMgZ2l2ZSB0aGUgZXhhY3QgcGxhY2VzIHdoZXJlIHRoZSBBUEkNCj4gY2hhbmdlcyBtYXkg
bm90IGJlIHJpZ2h0IGFzIHlvdSd2ZSBhbHJlYWR5IGRvbmUgaW4gdjEgYW5kIHYyLCBzbw0KPiB0
aGF0IEkgY2FuIGNvcnJlY3QgdGhlbS4NCg0KSSdsbCB0cnkgdG8gZmluZCB0aW1lIHRvIGxvb2sg
bGF0ZXIgdG9kYXkuDQoNCglEYXZpZA0KDQotDQpSZWdpc3RlcmVkIEFkZHJlc3MgTGFrZXNpZGUs
IEJyYW1sZXkgUm9hZCwgTW91bnQgRmFybSwgTWlsdG9uIEtleW5lcywgTUsxIDFQVCwgVUsNClJl
Z2lzdHJhdGlvbiBObzogMTM5NzM4NiAoV2FsZXMpDQo
next prev parent reply other threads:[~2019-10-17 9:04 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 6:14 [PATCHv3 net-next 0/5] sctp: update from rfc7829 Xin Long
2019-10-14 6:14 ` Xin Long
2019-10-14 6:14 ` [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification Xin Long
2019-10-14 6:14 ` Xin Long
2019-10-14 6:14 ` [PATCHv3 net-next 2/5] sctp: add pf_expose per netns and sock and asoc Xin Long
2019-10-14 6:14 ` Xin Long
2019-10-14 6:14 ` [PATCHv3 net-next 3/5] sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt Xin Long
2019-10-14 6:14 ` Xin Long
2019-10-14 6:14 ` [PATCHv3 net-next 4/5] sctp: add support for Primary Path Switchover Xin Long
2019-10-14 6:14 ` Xin Long
2019-10-14 6:14 ` [PATCHv3 net-next 5/5] sctp: add SCTP_PEER_ADDR_THLDS_V2 sockopt Xin Long
2019-10-14 6:14 ` Xin Long
2019-10-25 3:25 ` [PATCHv3 net-next 4/5] sctp: add support for Primary Path Switchover Marcelo Ricardo Leitner
2019-10-25 3:25 ` Marcelo Ricardo Leitner
2019-10-25 8:13 ` Xin Long
2019-10-25 8:13 ` Xin Long
2019-10-25 3:24 ` [PATCHv3 net-next 3/5] sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt Marcelo Ricardo Leitner
2019-10-25 3:24 ` Marcelo Ricardo Leitner
2019-10-25 8:05 ` Xin Long
2019-10-25 8:05 ` Xin Long
2019-10-25 3:23 ` [PATCHv3 net-next 2/5] sctp: add pf_expose per netns and sock and asoc Marcelo Ricardo Leitner
2019-10-25 3:23 ` Marcelo Ricardo Leitner
2019-10-25 8:02 ` Xin Long
2019-10-25 8:02 ` Xin Long
2019-10-25 9:00 ` David Laight
2019-10-25 9:00 ` David Laight
2019-10-25 13:21 ` 'Marcelo Ricardo Leitner'
2019-10-25 13:21 ` 'Marcelo Ricardo Leitner'
2019-10-25 14:26 ` David Laight
2019-10-25 14:26 ` David Laight
2019-10-25 14:45 ` 'Marcelo Ricardo Leitner'
2019-10-25 14:45 ` 'Marcelo Ricardo Leitner'
2019-10-18 15:56 ` [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification David Laight
2019-10-18 15:56 ` David Laight
2019-10-19 8:55 ` Xin Long
2019-10-19 8:55 ` Xin Long
2019-10-22 11:13 ` Xin Long
2019-10-22 11:13 ` Xin Long
2019-10-25 3:22 ` Marcelo Ricardo Leitner
2019-10-25 3:22 ` Marcelo Ricardo Leitner
2019-10-25 7:58 ` Xin Long
2019-10-25 7:58 ` Xin Long
2019-10-25 3:21 ` Marcelo Ricardo Leitner
2019-10-25 3:21 ` Marcelo Ricardo Leitner
2019-10-25 7:59 ` Xin Long
2019-10-25 7:59 ` Xin Long
2019-10-14 12:42 ` [PATCHv3 net-next 0/5] sctp: update from rfc7829 Neil Horman
2019-10-14 12:42 ` Neil Horman
2019-10-16 0:56 ` David Miller
2019-10-16 0:56 ` David Miller
2019-10-16 10:42 ` David Laight
2019-10-17 4:56 ` Xin Long
2019-10-17 4:56 ` Xin Long
2019-10-17 9:04 ` David Laight [this message]
2019-10-17 9:04 ` David Laight
2019-10-16 18:25 ` David Miller
2019-10-16 18:25 ` David Miller
2019-10-16 18:32 ` Marcelo Ricardo Leitner
2019-10-16 18:32 ` Marcelo Ricardo Leitner
2019-10-16 19:04 ` David Miller
2019-10-16 19:04 ` 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=a62ea0845f224f15ad42cf9818040919@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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.