From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: lucien.xin@gmail.com, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, nhorman@tuxdriver.com,
david.laight@aculab.com
Subject: Re: [PATCHv3 net-next 0/5] sctp: update from rfc7829
Date: Wed, 16 Oct 2019 18:32:09 +0000 [thread overview]
Message-ID: <20191016183209.GA4250@localhost.localdomain> (raw)
In-Reply-To: <20191016.142534.1360443052637911866.davem@davemloft.net>
On Wed, Oct 16, 2019 at 02:25:34PM -0400, David Miller wrote:
> From: Xin Long <lucien.xin@gmail.com>
> Date: Mon, 14 Oct 2019 14:14:43 +0800
>
> > SCTP-PF was implemented based on a Internet-Draft in 2012:
> >
> > https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
> >
> > It's been updated quite a few by rfc7829 in 2016.
> >
> > This patchset adds the following features:
>
> Sorry but I'm tossing these until an knowledgable SCTP person can
> look at them.
Hi Dave,
Maybe the email didn't get through but Neil actually already acked it,
2 days ago.
Message-ID: <20191014124249.GB11844@hmswarspite.think-freely.org>
I won't be able to review it :-(
Thanks,
Marcelo
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: lucien.xin@gmail.com, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, nhorman@tuxdriver.com,
david.laight@aculab.com
Subject: Re: [PATCHv3 net-next 0/5] sctp: update from rfc7829
Date: Wed, 16 Oct 2019 15:32:09 -0300 [thread overview]
Message-ID: <20191016183209.GA4250@localhost.localdomain> (raw)
In-Reply-To: <20191016.142534.1360443052637911866.davem@davemloft.net>
On Wed, Oct 16, 2019 at 02:25:34PM -0400, David Miller wrote:
> From: Xin Long <lucien.xin@gmail.com>
> Date: Mon, 14 Oct 2019 14:14:43 +0800
>
> > SCTP-PF was implemented based on a Internet-Draft in 2012:
> >
> > https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
> >
> > It's been updated quite a few by rfc7829 in 2016.
> >
> > This patchset adds the following features:
>
> Sorry but I'm tossing these until an knowledgable SCTP person can
> look at them.
Hi Dave,
Maybe the email didn't get through but Neil actually already acked it,
2 days ago.
Message-ID: <20191014124249.GB11844@hmswarspite.think-freely.org>
I won't be able to review it :-(
Thanks,
Marcelo
next prev parent reply other threads:[~2019-10-16 18:32 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
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 [this message]
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=20191016183209.GA4250@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=david.laight@aculab.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@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.