From: Slavomir Kaslev <kaslevs@vmware.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
slavomir.kaslev@gmail.com
Subject: [PATCH 0/2] Add note on splice/tee EAGAIN error when called with nonblocking descriptors
Date: Fri, 12 Apr 2019 17:02:45 +0300 [thread overview]
Message-ID: <20190412140247.9897-1-kaslevs@vmware.com> (raw)
Document that splice(2)/tee(2) can fail with EAGAIN when called with nonblocking
file descriptors and the operation would block.
Slavomir Kaslev (2):
splice.2: Note EAGAIN can occur when called on nonblocking file
descriptors
tee.2: Note EAGAIN can occur when called on nonblocking file
descriptors
man2/splice.2 | 4 +++-
man2/tee.2 | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.19.1
next reply other threads:[~2019-04-12 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 14:02 Slavomir Kaslev [this message]
2019-04-12 14:02 ` [PATCH 1/2] splice.2: Note EAGAIN can occur when called on nonblocking file descriptors Slavomir Kaslev
2019-05-05 10:29 ` Michael Kerrisk (man-pages)
2019-04-12 14:02 ` [PATCH 2/2] tee.2: " Slavomir Kaslev
2019-05-05 10:29 ` Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190412140247.9897-1-kaslevs@vmware.com \
--to=kaslevs@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=slavomir.kaslev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).