Cyril Hrubis <chrubis@xxxxxxx> writes: > Hi! >> > > So should we settle for memset()? I could update send updated patch >> > > then. >> > >> > Yeah, memset is what I typically have done. >> > >> >> Here comes updated patch. > > I've checked the latest man pages git and these changes aren't there > yet. Any comments? >> @@ -42,8 +42,12 @@ Link with \fI\-laio\fP. >> .BR io_setup () >> creates an asynchronous I/O context capable of receiving >> at least \fInr_events\fP. >> -\fIctxp\fP must not point to an AIO context that already exists, and must >> +The \fIctxp\fP must not point to an AIO context that already exists, and must >> be initialized to 0 prior to the call. >> + >> +Note that io_context_t is opaque type and thuss \fIctxp\fP should be zeroed One extra 's' in thus. other than that, looks good to me. -Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
