From fb456e00ac34be0558b9fc767185ba3fe2247f1d Mon Sep 17 00:00:00 2001 From: Edgar Bonet Date: Tue, 5 May 2015 16:27:21 +0200 Subject: [PATCH] Fix documentation of TCP_WRITE_FLAG_MORE. The description of the flag was erroneous in src/core/tcp_out.c, and self-contradictory in doc/rawapi.txt. --- doc/rawapi.txt | 2 +- src/core/tcp_out.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/rawapi.txt b/doc/rawapi.txt index 8c190305..f5f80fad 100644 --- a/doc/rawapi.txt +++ b/doc/rawapi.txt @@ -196,7 +196,7 @@ callback function. should be allocated and the data should only be referenced by pointer. This also means that the memory behind dataptr must not change until the data is ACKed by the remote host - - TCP_WRITE_FLAG_MORE: indicates that more data follows. If this is given, + - TCP_WRITE_FLAG_MORE: indicates that more data follows. If this is omitted, the PSH flag is set in the last segment created by this call to tcp_write. If this flag is given, the PSH flag is not set. diff --git a/src/core/tcp_out.c b/src/core/tcp_out.c index ec42164b..98bae81f 100644 --- a/src/core/tcp_out.c +++ b/src/core/tcp_out.c @@ -364,7 +364,7 @@ tcp_write_checks(struct tcp_pcb *pcb, u16_t len) * @param len Data length in bytes * @param apiflags combination of following flags : * - TCP_WRITE_FLAG_COPY (0x01) data will be copied into memory belonging to the stack - * - TCP_WRITE_FLAG_MORE (0x02) for TCP connection, PSH flag will be set on last segment sent, + * - TCP_WRITE_FLAG_MORE (0x02) for TCP connection, PSH flag will not be set on last segment sent, * @return ERR_OK if enqueued, another err_t on error */ err_t