From: domen@coderock.org
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, domen@coderock.org, wharms@bfs.de
Subject: [patch 3/8] string.linux-2.6.10/lib/c: documentation strncpy()
Date: Fri, 08 Apr 2005 09:50:56 +0200 [thread overview]
Message-ID: <20050408075057.3C9EE1EE91@trashy.coderock.org> (raw)
this clarifys the documentation on the behavier of strncpy().
Signed-off-by: Domen Puncer <domen@coderock.org>
---
kj-domen/lib/string.c | 4 ++++
1 files changed, 4 insertions(+)
diff -L lib/c.bak -puN /dev/null /dev/null
diff -puN lib/string.c~comment-lib_string lib/string.c
--- kj/lib/string.c~comment-lib_string 2005-04-05 12:57:42.000000000 +0200
+++ kj-domen/lib/string.c 2005-04-05 12:57:42.000000000 +0200
@@ -85,6 +85,10 @@ EXPORT_SYMBOL(strcpy);
*
* The result is not %NUL-terminated if the source exceeds
* @count bytes.
+ *
+ * In the case where the length of @src is less than that of
+ * count, the remainder of @dest will be padded with %NUL.
+ *
*/
char * strncpy(char * dest,const char *src,size_t count)
{
_
next reply other threads:[~2005-04-08 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 7:50 domen [this message]
2005-04-08 18:25 ` [patch 3/8] lib/c: documentation strncpy() Domen Puncer
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=20050408075057.3C9EE1EE91@trashy.coderock.org \
--to=domen@coderock.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wharms@bfs.de \
/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