From: Xin Long <lucien.xin@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Vladislav Yasevich <vyasevich@gmail.com>,
daniel@iogearbox.net
Subject: Re: [PATCHv2 net 0/5] sctp: some fixes of prsctp polices
Date: Thu, 29 Sep 2016 00:29:30 +0800 [thread overview]
Message-ID: <CADvbK_fAgk3hvEaR4zZjuH_ch9AbLkM3pSk_B7bHGmrpnsZRvQ@mail.gmail.com> (raw)
In-Reply-To: <20160928.111716.1982951742537758888.davem@davemloft.net>
>
> That doesn't matter. This happens all the time.
>
> The way you handle this is you submit patch #1 targetting 'net' and
> wait for it to get into 'net' and propagate into 'net-next'. When
> that happens you can submit patches #2-5 as a second patch series
> targetting 'net-next'.
Thanks, will reorganize them.
prev parent reply other threads:[~2016-09-28 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 10:46 [PATCHv2 net 0/5] sctp: some fixes of prsctp polices Xin Long
2016-09-28 10:46 ` [PATCHv2 net 1/5] sctp: move sent_count to the memory hole in sctp_chunk Xin Long
2016-09-28 10:46 ` [PATCHv2 net 2/5] sctp: reuse sent_count to avoid retransmitted chunks for RTT measurements Xin Long
2016-09-28 10:46 ` [PATCHv2 net 3/5] sctp: remove prsctp_param from sctp_chunk Xin Long
2016-09-28 10:46 ` [PATCHv2 net 4/5] sctp: change to check peer prsctp_capable when using prsctp polices Xin Long
2016-09-28 10:46 ` [PATCHv2 net 5/5] sctp: remove the old ttl expires policy Xin Long
2016-09-28 11:22 ` [PATCHv2 net 0/5] sctp: some fixes of prsctp polices Marcelo Ricardo Leitner
2016-09-28 12:13 ` David Miller
2016-09-28 12:35 ` Xin Long
2016-09-28 15:17 ` David Miller
2016-09-28 15:44 ` marcelo.leitner
2016-09-28 16:29 ` Xin Long [this message]
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=CADvbK_fAgk3hvEaR4zZjuH_ch9AbLkM3pSk_B7bHGmrpnsZRvQ@mail.gmail.com \
--to=lucien.xin@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).