Make it explicit that the use of common sense is required when applying
the rules of the style guide.  Also point out explicitly that in
multiple variable declarations, you're supposed to "violate" an earlier
rule.

Reviewed-by: Gleb Natapov <gleb@cloudius-systems.com>
Signed-off-by: Pekka Enberg <penberg@cloudius-systems.com>

C++ coding convention is to bind '*' and '&' to the type,
not to the variable.

Signed-off-by: Zhi Yong Wu <zwu.kernel@gmail.com>
Signed-off-by: Pekka Enberg <penberg@cloudius-systems.com>

Signed-off-by: Zhi Yong Wu <zwu.kernel@gmail.com>
Signed-off-by: Pekka Enberg <penberg@cloudius-systems.com>

Some more coding style issues collected from reviews over the last few
days (mostly from Avi).

Signed-off-by: Nadav Har'El <nyh@cloudius-systems.com>
Signed-off-by: Avi Kivity <avi@cloudius-systems.com>

Add to our coding conventions, CODINGSTYLE.md, three coding conventions
which were mentioned by Avi Kivity in a review, and also fit most of our
code. These conventions are:

 1. No (void) in function declarations in C++ code.
 2. No space between function name and argument list.
 3. No parantheses around return value.

Signed-off-by: Nadav Har'El <nyh@cloudius-systems.com>
Signed-off-by: Pekka Enberg <penberg@cloudius-systems.com>

This document describe OSv coding style.

Signed-off-by: Amnon Heiman <amnon@cloudius-systems.com>
Signed-off-by: Pekka Enberg <penberg@cloudius-systems.com>