From: Peter Radisson <radisson97@web.de>
To: linux-man@vger.kernel.org,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Subject: [PATCH] make consistent example in recv.2
Date: Thu, 27 Mar 2025 18:54:00 +0100 [thread overview]
Message-ID: <189ef077-18f4-43a3-9008-286a75e7bd91@web.de> (raw)
Replace 0 with NULL als in the example a few lines above
---
man2/recv.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man2/recv.2 b/man2/recv.2
index ba17d03a3..21f65e86f 100644
--- a/man2/recv.2
+++ b/man2/recv.2
@@ -325,7 +325,7 @@ socket (see
.BR connect (2)).
It is equivalent to the call:
.PP
- recvfrom(fd, buf, len, flags, NULL, 0);
+ recvfrom(fd, buf, len, flags, NULL, NULL);
.\"
.SS recvmsg()
The
--
2.35.3
next reply other threads:[~2025-03-27 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 17:54 Peter Radisson [this message]
2025-03-28 22:53 ` [PATCH] make consistent example in recv.2 Carlos O'Donell
2025-03-29 18:30 ` Alejandro Colomar
2025-04-01 19:22 ` Peter Radisson
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=189ef077-18f4-43a3-9008-286a75e7bd91@web.de \
--to=radisson97@web.de \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
/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