From: Ivo Calado <ivocalado@embedded.ufcg.edu.br>
To: Gerrit Renker <gerrit@erg.abdn.ac.uk>,
dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 5/5] Updating documentation accordingly
Date: Mon, 14 Sep 2009 21:41:13 -0300 [thread overview]
Message-ID: <cb00fa210909141741r54cd541fi242b110a727fbfcc@mail.gmail.com> (raw)
In-Reply-To: <20090913185050.GA7475@gerrit.erg.abdn.ac.uk>
On Sun, Sep 13, 2009 at 15:50, Gerrit Renker <gerrit@erg.abdn.ac.uk> wrote:
> | Updating documentation accordingly
>
> +/* As defined at section 8.6.1. of RFC 4342 */
> #define TFRC_LOSS_INTERVALS_OPT_MAX_LENGTH 28
> +/* Specified on section 8.7. of CCID4 draft */
> #define TFRC_DROP_OPT_MAX_LENGTH 84
> Need to update the references to CCID4 draft with RFC 5622. See also 4/5.
>
> It would be more helpful to include the documentation for structs with
> the patches that use these structs.
>
Thanks, I'll fix this.
--
Ivo Augusto Andrade Rocha Calado
MSc. Candidate
Embedded Systems and Pervasive Computing Lab - http://embedded.ufcg.edu.br
Systems and Computing Department - http://www.dsc.ufcg.edu.br
Electrical Engineering and Informatics Center - http://www.ceei.ufcg.edu.br
Federal University of Campina Grande - http://www.ufcg.edu.br
PGP: 0x03422935
Quidquid latine dictum sit, altum viditur.
next prev parent reply other threads:[~2009-09-15 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 18:28 [PATCH 5/5] Updating documentation accordingly Ivo Calado
2009-09-13 18:50 ` Gerrit Renker
2009-09-15 0:41 ` Ivo Calado [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 12:25 Ivo Calado
2009-09-04 15:45 ` Randy Dunlap
[not found] <cb00fa210909011736t3629163ch2753c3f43e1a9601@mail.gmail.com>
2009-09-02 2:46 ` Ivo Calado
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=cb00fa210909141741r54cd541fi242b110a727fbfcc@mail.gmail.com \
--to=ivocalado@embedded.ufcg.edu.br \
--cc=dccp@vger.kernel.org \
--cc=gerrit@erg.abdn.ac.uk \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).