From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 3/3]: Update computation of X to use newer timeofday interface
Date: Mon, 11 Jun 2007 08:39:08 +0000 [thread overview]
Message-ID: <200706110939.08144@strip-the-willow> (raw)
In-Reply-To: <200706091933.09514@strip-the-willow>
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.
next prev parent reply other threads:[~2007-06-11 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-09 18:33 [PATCH 3/3]: Update computation of X to use newer timeofday interface Gerrit Renker
2007-06-10 6:05 ` Ian McDonald
2007-06-11 8:39 ` Gerrit Renker [this message]
2007-06-16 16:29 ` Arnaldo Carvalho de Melo
2007-06-16 16:45 ` Gerrit Renker
2007-06-16 16:55 ` Arnaldo Carvalho de Melo
2007-06-16 17:11 ` Gerrit Renker
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=200706110939.08144@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=dccp@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.