wireguard-monolithic-historical - Historical monolithic WireGuard repository, split into wireguard-tools, wireguard-linux, and wireguard-linux-compat.

	Commit message (Collapse)	Author	Age	Files	Lines
*	headers: cleanup notices	Jason A. Donenfeld	2016-11-21	1	-1/+1
\|
*	socket: keep track of src address in sending packets	Jason A. Donenfeld	2016-11-15	1	-1/+1
\|
*	c89: the static keyword is okay in c99, but not in c89	Jason A. Donenfeld	2016-11-05	1	-1/+1
\|
*	socket: use dst_cache instead of handrolled cache	Jason A. Donenfeld	2016-11-04	1	-2/+6
\|
*	timers: take reference like a lookup table	Jason A. Donenfeld	2016-11-03	1	-8/+15
\|
*	kref: elide checks	Jason A. Donenfeld	2016-11-02	1	-5/+3
\|
*	peer: kref is most likely to succeed	Jason A. Donenfeld	2016-11-01	1	-2/+2
\|
*	Rework headers and includes	Jason A. Donenfeld	2016-09-29	1	-5/+2
\|
*	c: specify static array size in function params	Jason A. Donenfeld	2016-08-02	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The C standard states: A declaration of a parameter as ``array of type'' shall be adjusted to ``qualified pointer to type'', where the type qualifiers (if any) are those specified within the [ and ] of the array type derivation. If the keyword static also appears within the [ and ] of the array type derivation, then for each call to the function, the value of the corresponding actual argument shall provide access to the first element of an array with at least as many elements as specified by the size expression. By changing void func(int array[4]) to void func(int array[static 4]), we automatically get the compiler checking argument sizes for us, which is quite nice.
*	Initial commit	Jason A. Donenfeld	2016-06-25	1	-0/+144