From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: [PATCH 1/4] io_cancel.2: fix up the description Date: Thu, 4 Apr 2013 15:36:55 -0400 Message-ID: <1365104218-26042-2-git-send-email-jmoyer@redhat.com> References: <1365104218-26042-1-git-send-email-jmoyer@redhat.com> Return-path: In-Reply-To: <1365104218-26042-1-git-send-email-jmoyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: chrubis-AlSwsSmVLrQ@public.gmane.org, mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, Jeff Moyer List-Id: linux-man@vger.kernel.org The description for this sytem call was a bit inaccurate. Cyril still takes issue with my wording, so this is up for further word-smithing, I think. I'm open to suggestions. Signed-off-by: Jeff Moyer --- man2/io_cancel.2 | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/man2/io_cancel.2 b/man2/io_cancel.2 index 0f974ed..6adddf3 100644 --- a/man2/io_cancel.2 +++ b/man2/io_cancel.2 @@ -26,10 +26,10 @@ attempts to cancel an asynchronous I/O operation previously submitted with .BR io_submit (2). The .I ctx_id -argument is the AIO context ID of the operation to be canceled. -If the AIO context is found, the event will be canceled and then copied -into the memory pointed to by \fIresult\fP without being placed -into the completion queue. +argument is the AIO context ID into which the operation was submitted. +If the operation is successfully canceled, the event will be copied into +the memory pointed to by \fIresult\fP without being placed into the +completion queue. .SH RETURN VALUE On success, .BR io_cancel () -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html