From: 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,
vyasevich@gmail.com
Subject: Re: [PATCHv4 net-next 3/5] sctp: implement sender-side procedures for SSN/TSN Reset Request Paramete
Date: Fri, 20 Jan 2017 20:47:01 +0000 [thread overview]
Message-ID: <20170120204701.GW3781@localhost.localdomain> (raw)
In-Reply-To: <20170120.140034.1018095629148946810.davem@davemloft.net>
On Fri, Jan 20, 2017 at 02:00:34PM -0500, David Miller wrote:
> From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
> Date: Fri, 20 Jan 2017 16:25:22 -0200
>
> > I talked offline with Xin about this and we cannot do it this way.
> > Unfortunatelly we will have to take the long road here, because then
> > we may send data while sending the request, as the streams are not
> > closed yet. We really need to close team, send the request, and
> > re-open if the send fails.
>
> I am expecting another spin of this series, correct?
Yes.
WARNING: multiple messages have this Message-ID (diff)
From: 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,
vyasevich@gmail.com
Subject: Re: [PATCHv4 net-next 3/5] sctp: implement sender-side procedures for SSN/TSN Reset Request Parameter
Date: Fri, 20 Jan 2017 18:47:01 -0200 [thread overview]
Message-ID: <20170120204701.GW3781@localhost.localdomain> (raw)
In-Reply-To: <20170120.140034.1018095629148946810.davem@davemloft.net>
On Fri, Jan 20, 2017 at 02:00:34PM -0500, David Miller wrote:
> From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
> Date: Fri, 20 Jan 2017 16:25:22 -0200
>
> > I talked offline with Xin about this and we cannot do it this way.
> > Unfortunatelly we will have to take the long road here, because then
> > we may send data while sending the request, as the streams are not
> > closed yet. We really need to close team, send the request, and
> > re-open if the send fails.
>
> I am expecting another spin of this series, correct?
Yes.
next prev parent reply other threads:[~2017-01-20 20:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 18:00 [PATCHv4 net-next 0/5] sctp: add sender-side procedures for stream reconf asoc reset and add streams Xin Long
2017-01-20 18:00 ` Xin Long
2017-01-20 18:00 ` [PATCHv4 net-next 1/5] sctp: streams should be closed when stream reset request is sent successfully Xin Long
2017-01-20 18:00 ` Xin Long
2017-01-20 18:00 ` [PATCHv4 net-next 2/5] sctp: add support for generating stream reconf ssn/tsn reset request chunk Xin Long
2017-01-20 18:00 ` Xin Long
2017-01-20 18:00 ` [PATCHv4 net-next 3/5] sctp: implement sender-side procedures for SSN/TSN Reset Request Parameter Xin Long
2017-01-20 18:00 ` Xin Long
2017-01-20 18:00 ` [PATCHv4 net-next 4/5] sctp: add support for generating stream reconf add incoming/outgoing streams Xin Long
2017-01-20 18:00 ` [PATCHv4 net-next 4/5] sctp: add support for generating stream reconf add incoming/outgoing streams request chunk Xin Long
2017-01-20 18:00 ` [PATCHv4 net-next 5/5] sctp: implement sender-side procedures for Add Incoming/Outgoing Streams Requ Xin Long
2017-01-20 18:00 ` [PATCHv4 net-next 5/5] sctp: implement sender-side procedures for Add Incoming/Outgoing Streams Request Parameter Xin Long
2017-01-20 18:25 ` [PATCHv4 net-next 3/5] sctp: implement sender-side procedures for SSN/TSN Reset Request Paramete Marcelo Ricardo Leitner
2017-01-20 18:25 ` [PATCHv4 net-next 3/5] sctp: implement sender-side procedures for SSN/TSN Reset Request Parameter Marcelo Ricardo Leitner
2017-01-20 19:00 ` [PATCHv4 net-next 3/5] sctp: implement sender-side procedures for SSN/TSN Reset Request Paramete David Miller
2017-01-20 19:00 ` [PATCHv4 net-next 3/5] sctp: implement sender-side procedures for SSN/TSN Reset Request Parameter David Miller
2017-01-20 20:47 ` marcelo.leitner [this message]
2017-01-20 20:47 ` marcelo.leitner
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=20170120204701.GW3781@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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.