[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160928.111716.1982951742537758888.davem@davemloft.net>
Date: Wed, 28 Sep 2016 11:17:16 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: lucien.xin@...il.com
Cc: netdev@...r.kernel.org, linux-sctp@...r.kernel.org,
marcelo.leitner@...il.com, vyasevich@...il.com,
daniel@...earbox.net
Subject: Re: [PATCHv2 net 0/5] sctp: some fixes of prsctp polices
From: Xin Long <lucien.xin@...il.com>
Date: Wed, 28 Sep 2016 20:35:40 +0800
>>
>>> This patchset is to improve some codes about prsctp polices, and also
>>> to fix some issues.
>>>
>>> v1->v2:
>>> - wrap the check of chunk->sent_count in a macro:
>>> sctp_chunk_retransmitted in patch 2/5.
>>
>> This series is a mix of bug fixes (patch #1) which should be targetting
>> 'net' and simplifications/cleanups (patch #2-5) which should be targetting
>> 'net-next'.
>>
>> Please do not mix things up like this, and submit patches targetting
>> the appropriate tree.
>>
> understand, I wanted to divide them.
> but this patchset is special, the following patches
> depend on patch 1/5.
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'.
Powered by blists - more mailing lists