From 67146ae418f2308e3da0221ce2d74827c2dab7b7 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Sat, 26 Mar 2011 15:57:25 -0400 Subject: Startlingly, memcpy() is *less* of a problem for the seqlock than I thought. --- shmexport.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'shmexport.c') 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 -- cgit v1.2.1