aboutsummaryrefslogtreecommitdiff
path: root/nuttx/ChangeLog
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2013-01-20 00:41:33 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2013-01-20 00:41:33 +0000
commit28a0cf4aa03e0a43d63492844ef3f3eee9da84a5 (patch)
treec6747a24d9b95fcc7d54938f8cbbcc0cd7bfca06 /nuttx/ChangeLog
parent598b4b28793536198ffd145b895e2821334332da (diff)
downloadpx4-firmware-28a0cf4aa03e0a43d63492844ef3f3eee9da84a5.tar.gz
px4-firmware-28a0cf4aa03e0a43d63492844ef3f3eee9da84a5.tar.bz2
px4-firmware-28a0cf4aa03e0a43d63492844ef3f3eee9da84a5.zip
Yet another repair for the previouis botched recvfrom() fix; Fix telnet driver: It needs to break out of the read loop if 0 (meaning not conneced) of a value < 0 (an error) is encountered.
git-svn-id: http://svn.code.sf.net/p/nuttx/code/trunk@5541 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/ChangeLog')
-rw-r--r--nuttx/ChangeLog3
1 files changed, 3 insertions, 0 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog
index 80944db66..77441dd21 100644
--- a/nuttx/ChangeLog
+++ b/nuttx/ChangeLog
@@ -3993,3 +3993,6 @@
(gracefully). recv[from]() returned success and the closure
was never detected. Hmmm.. I don't know why the network monitor
did not catch this event. This is an important bug fix.
+ * net/recvfrom(): Fix a introduced with the last bugfix. If
+ the peer does an orderly closure of the socket, report 0 not
+ -ENOTCONN