wireguard-openbsd/lib/libc/gen/valloc.3, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/lib/libc/gen/valloc.3?h=jd%2Fqueueboosts 2018-11-05T10:31:32Z Mention aligned_alloc(), prompted by Brad; ok jmc@ 2018-11-05T10:31:32Z otto otto@openbsd.org 2018-11-05T10:31:32Z urn:sha1:71fd22b5f38baf38f590ef5af2f5a4fd5ad80d6d Use the fancy .In macro for includes. From Jan Klemkow. ok jmc schwarze 2013-06-05T03:39:22Z tedu tedu@openbsd.org 2013-06-05T03:39:22Z urn:sha1:64d4e9871d1af4e50715ace8f2f237ff8e4d36e0 add posix_madvise, posix_memalign, strndup, and strnlen. mostly from 2010-05-18T22:24:54Z tedu tedu@openbsd.org 2010-05-18T22:24:54Z urn:sha1:243f393511fee0e3dea053d89336d8b8f85b60ee brad and millert, with hints from guenther, jmc, and otto I think. ok previous. convert to new .Dd format; 2007-05-31T19:19:00Z jmc jmc@openbsd.org 2007-05-31T19:19:00Z urn:sha1:9490d37cb6a2f9c8feb8d4b7f9c43b2ac41784aa - sync prototypes and header file excerpts to reality 2005-07-22T03:16:58Z jaredy jaredy@openbsd.org 2005-07-22T03:16:58Z urn:sha1:7bac872d42eb6260419ef7f2f38ef944d92edce9 - many grammar, punctuation, macro, layout, spelling/typos, rewording, etc. fixes - avoid first person - sprinkle crossrefs where relevant help & ok jmc Remove the advertising clause in the UCB license which Berkeley 2003-06-02T20:18:29Z millert millert@openbsd.org 2003-06-02T20:18:29Z urn:sha1:6580fee3295c971a919cc04bfc3598c5f8bcd2b1 rescinded 22 July 1999. Proofed by myself and Theo. Various repairs, mostly to get rid of short lines. 2000-12-24T00:30:46Z aaron aaron@openbsd.org 2000-12-24T00:30:46Z urn:sha1:50772e640915b6b9c44cb3d6508fa0a5fff413ef - remove all trailing whitespace 1999-07-09T13:35:13Z aaron aaron@openbsd.org 1999-07-09T13:35:13Z urn:sha1:5c3dced36cf8ba5814dbe5ef397db72526a1fd4f * except when it is escaped with a `\' at the end of the line - fix remaining .Nm usage as well - this is from a patch I received from kwesterback@home.com, who has been working on some scripts for fixing formatting errors in mdoc'd man pages Ok, so there could be a cost/benefit debate with this commit, but since I have the patch we might as well commit it... After some constructive criticism from pjanzen@ and some e-mail tag: 1999-06-04T01:30:10Z aaron aaron@openbsd.org 1999-06-04T01:30:10Z urn:sha1:545403d5ba85af10b0396609ee9da69f3c14f513 - only use the .Dv NULL form when referring explicitly to a function argument or return value - otherwise, use these forms: o non-null o null-terminated (hyphenated form for predicate adjective) o else, null terminated, or null terminate, whichever the case o null pointer, null byte, null string, etc. - may use NUL to refer to an ASCII NUL, but it doesn't need a .Tn macro In general, capitalizing the word "null" everywhere is unnecessary and makes the man pages harder to read. The above is consistent with popular programming texts (i.e., K&R, Stevens). repairs; go back over some old files, because we should properly distinguish 1999-05-29T22:38:33Z aaron aaron@openbsd.org 1999-05-29T22:38:33Z urn:sha1:d7403a2a9920cef3553a58e7c79772e68b7335a3 between NUL and NULL, i.e., don't use the .Dv (defined variable) macro when referring to an ASCII NUL