From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Neil Horman <nhorman@tuxdriver.com>,
network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>
Subject: Re: [PATCHv2 net-next 0/5] sctp: add support for generating stream reconf chunks
Date: Mon, 9 Jan 2017 17:04:24 -0200 [thread overview]
Message-ID: <20170109190424.GE3781@localhost.localdomain> (raw)
In-Reply-To: <CADvbK_dE74bAoTNo9gLczLuj71w3WMcPJ56tCFGJ=XjTMtTgRw@mail.gmail.com>
On Tue, Jan 10, 2017 at 02:27:09AM +0800, Xin Long wrote:
> On Mon, Jan 9, 2017 at 11:53 PM, David Miller <davem@davemloft.net> wrote:
> > From: Neil Horman <nhorman@tuxdriver.com>
> > Date: Mon, 9 Jan 2017 07:43:25 -0500
> >
> >> These all look reasonably good, but it seems before we accept them,
> >> there should be an additional patch that actually makes use of the code.
> >> I presume that is forthcomming?
> >
> > This all comes from my asking that the original huge set of patches be
> > split up.
> >
> > People always just rush this kind of work and never think about laying
> > out the resubmission properly.
> >
> > One should always only submit new interfaces along with an actual use
> > because only with a use can we properly review whether the new
> > interface is good or not.
>
> I was trying to keep the same order with rfc, but it seems not a good
> idea, will resplit, thanks.
Not sure how much it can help but one idea it to split it into requester
and requested sides. Do the first patches/patchsets to make Linux able
to accept/handle requests, and then to issue requests.
Marcelo
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Neil Horman <nhorman@tuxdriver.com>,
network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>
Subject: Re: [PATCHv2 net-next 0/5] sctp: add support for generating stream reconf chunks
Date: Mon, 09 Jan 2017 19:04:24 +0000 [thread overview]
Message-ID: <20170109190424.GE3781@localhost.localdomain> (raw)
In-Reply-To: <CADvbK_dE74bAoTNo9gLczLuj71w3WMcPJ56tCFGJ=XjTMtTgRw@mail.gmail.com>
On Tue, Jan 10, 2017 at 02:27:09AM +0800, Xin Long wrote:
> On Mon, Jan 9, 2017 at 11:53 PM, David Miller <davem@davemloft.net> wrote:
> > From: Neil Horman <nhorman@tuxdriver.com>
> > Date: Mon, 9 Jan 2017 07:43:25 -0500
> >
> >> These all look reasonably good, but it seems before we accept them,
> >> there should be an additional patch that actually makes use of the code.
> >> I presume that is forthcomming?
> >
> > This all comes from my asking that the original huge set of patches be
> > split up.
> >
> > People always just rush this kind of work and never think about laying
> > out the resubmission properly.
> >
> > One should always only submit new interfaces along with an actual use
> > because only with a use can we properly review whether the new
> > interface is good or not.
>
> I was trying to keep the same order with rfc, but it seems not a good
> idea, will resplit, thanks.
Not sure how much it can help but one idea it to split it into requester
and requested sides. Do the first patches/patchsets to make Linux able
to accept/handle requests, and then to issue requests.
Marcelo
next prev parent reply other threads:[~2017-01-09 19:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 9:42 [PATCHv2 net-next 0/5] sctp: add support for generating stream reconf chunks Xin Long
2017-01-07 9:42 ` Xin Long
2017-01-07 9:42 ` [PATCHv2 net-next 1/5] sctp: add a common helper function to generate stream reconf chunk Xin Long
2017-01-07 9:42 ` Xin Long
2017-01-07 9:42 ` [PATCHv2 net-next 2/5] sctp: add support for generating stream reconf ssn reset request chunk Xin Long
2017-01-07 9:42 ` Xin Long
2017-01-07 9:43 ` [PATCHv2 net-next 3/5] sctp: add support for generating stream reconf ssn/tsn " Xin Long
2017-01-07 9:43 ` Xin Long
2017-01-07 9:43 ` [PATCHv2 net-next 4/5] sctp: add support for generating stream reconf response chunk Xin Long
2017-01-07 9:43 ` Xin Long
2017-01-07 9:43 ` [PATCHv2 net-next 5/5] sctp: add support for generating stream reconf add streams request chunk Xin Long
2017-01-07 9:43 ` Xin Long
2017-01-09 12:43 ` [PATCHv2 net-next 0/5] sctp: add support for generating stream reconf chunks Neil Horman
2017-01-09 12:43 ` Neil Horman
2017-01-09 15:53 ` David Miller
2017-01-09 15:53 ` David Miller
2017-01-09 18:27 ` Xin Long
2017-01-09 18:27 ` Xin Long
2017-01-09 18:53 ` David Miller
2017-01-09 18:53 ` David Miller
2017-01-09 19:04 ` Marcelo Ricardo Leitner [this message]
2017-01-09 19:04 ` Marcelo Ricardo 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=20170109190424.GE3781@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.