Should new code have forward declarations of static functions or not?

Is it preferred to have forward declarations of static funcs, or to omit them altogether? I know that different files in kernel code follow one style or the other. Just wondering if there's a preferred style for new code. Simon

Looking for way to program external MMU from userspace (or viable alternative)

Hi kernel community, We have an external PCIe board with a custom coprocessor on it. We also have code for a kernel driver for it. We have thought about upstreaming it, but we realized that we can instead convert the driver to a userspace driver using UIO. However, there's one aspect of the syste

[tip:perf/core] perf tools: Update documentation info about quipper

Commit-ID: 2acad19500c28ce0c4dc3f9bf1dcfc82040b6531 Gitweb: http://git.kernel.org/tip/2acad19500c28ce0c4dc3f9bf1dcfc82040b6531 Author: Simon Que AuthorDate: Wed, 28 Sep 2016 11:37:53 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 29 Sep 2016 11:16:44 -0300 perf tools

[tip:perf/core] perf symbols: Get kernel start address by symbol name

Commit-ID: a93f0e551af9e194db38bfe16001e17a3a1d189a Gitweb: http://git.kernel.org/tip/a93f0e551af9e194db38bfe16001e17a3a1d189a Author: Simon Que AuthorDate: Mon, 16 Jun 2014 11:32:09 -0700 Committer: Jiri Olsa CommitDate: Fri, 20 Jun 2014 09:34:22 +0200 perf symbols: Get kernel start

[PATCH v2] perf: Get kernel start address by symbol name

machine__get_kernel_start_addr() to search for the symbol "_text" or "_stext", which marks the beginning of kernel mapping. This was already being done in machine__create_kernel_maps(). Thus, this patch is just a refactor, to move that code into machine__get_kernel_start_addr(). Signed-off-by: S

[PATCH] perf: Get kernel start address by symbol name

t_addr(). Change-Id: I0c38c36f5e8b0f4fb92a6f57211fa45aabe545a6 Signed-off-by: Simon Que --- tools/perf/util/machine.c | 54 +++ 1 file changed, 22 insertions(+), 32 deletions(-) diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c index 620a198..acda3d2 100644 -

[PATCH] Add -Werror build option

Add a config option "ERROR_ON_WARNING" that adds the "-Werror" flag to gcc, which turns warnings into errors. This option enables developers to set a stricter level of code checking for kernel code: all code must be warning-free. Signed-off-by: Simon Que Signed-off-by: