From mboxrd@z Thu Jan  1 00:00:00 1970
From: Xin Long <lucien.xin@gmail.com>
Date: Wed, 28 Sep 2016 16:29:30 +0000
Subject: Re: [PATCHv2 net 0/5] sctp: some fixes of prsctp polices
Message-Id: <CADvbK_fAgk3hvEaR4zZjuH_ch9AbLkM3pSk_B7bHGmrpnsZRvQ@mail.gmail.com>
List-Id: <linux-sctp.vger.kernel.org>
References: <cover.1475059350.git.lucien.xin@gmail.com> <20160928.081303.661512609700070565.davem@davemloft.net>
 <CADvbK_eKrZaGf0uDsCBdkWCw9e51W-HVL=_WLsR4RaSKjNmqqA@mail.gmail.com> <20160928.111716.1982951742537758888.davem@davemloft.net>
In-Reply-To: <20160928.111716.1982951742537758888.davem@davemloft.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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

>
> 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.