From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xin Long Subject: Re: [PATCHv2 net 0/5] sctp: some fixes of prsctp polices Date: Thu, 29 Sep 2016 00:29:30 +0800 Message-ID: References: <20160928.081303.661512609700070565.davem@davemloft.net> <20160928.111716.1982951742537758888.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: network dev , linux-sctp@vger.kernel.org, Marcelo Ricardo Leitner , Vladislav Yasevich , daniel@iogearbox.net To: David Miller Return-path: Received: from mail-qk0-f181.google.com ([209.85.220.181]:35426 "EHLO mail-qk0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932916AbcI1Q3b (ORCPT ); Wed, 28 Sep 2016 12:29:31 -0400 In-Reply-To: <20160928.111716.1982951742537758888.davem@davemloft.net> Sender: netdev-owner@vger.kernel.org List-ID: > > 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.