Quoting Ian McDonald: | This looks OK but... | > -static void ccid3_hc_tx_update_x(struct sock *sk, struct timeval *now) | > +static void ccid3_hc_tx_update_x(struct sock *sk, ktime_t *stamp) | > | I don't see callers updated. Is this what you mean by patches being | interdependent? That is right - the callers are updated in the next bundle of patches. This set contains 29 patches in total, divided into the following sets: 1. ktime_t update [sent] 2. RTT and timestamping patches [sent] 3. CCID3 TX history - locking and migration to singly-linked list (suggestion by Arnaldo) => to be sent 4. Update of computation wrt draft rfc3448bis-00 => to be sent 5. Miscellaneous CCID3 patches => to be sent 6. Miscellaneous DCCP patches => to be sent The callers are updated in subset (4) - I will send that later today. These patches are first and foremost meant for the upcoming `experimental' tree, I was thinking that sending one or two bundles at a time is better than sending the whole 29 patches at once. Once they are in the tree, after going through this stage, the relationships are easier to see. Thus, interdependencies are unavoidable at this stage, but they have been minimised to quite a great degree: with some labour, 5 patches that overlapped with others were merged across 50 or so patches. Doing even more integration would make them less readable. - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
