summaryrefslogtreecommitdiff
path: root/shmexport.c
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2011-03-26 15:57:25 -0400
committerEric S. Raymond <esr@thyrsus.com>2011-03-26 15:57:25 -0400
commit67146ae418f2308e3da0221ce2d74827c2dab7b7 (patch)
tree77264e5d0436359f627446c1f93a899820792729 /shmexport.c
parent508f0d14817163182b03489edb4e0d8f12e51bc5 (diff)
downloadgpsd-67146ae418f2308e3da0221ce2d74827c2dab7b7.tar.gz
Startlingly, memcpy() is *less* of a problem for the seqlock than I thought.
Diffstat (limited to 'shmexport.c')
-rw-r--r--shmexport.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/shmexport.c b/shmexport.c
index 88d110bd..d881417b 100644
--- a/shmexport.c
+++ b/shmexport.c
@@ -74,7 +74,7 @@ void shm_update(struct gps_context_t *context, struct gps_data_t *gpsdata)
* the second bookend first, then the data, then the first bookend.
* Reader copies what it sees in normal order; that way, if we
* start to write the segment during the read, the second bookend will
- * get clobbered first and the data can be detected bad.
+ * get clobbered first and the data can be detected as bad.
*/
((struct shmexport_t *)context->shmexport)->bookend2 = tick;
#ifndef S_SPLINT_S