summaryrefslogtreecommitdiffstats
path: root/Documentation/networking/kcm.rst
diff options
context:
space:
mode:
authorMasahiro Yamada <masahiroy@kernel.org>2020-12-01 11:34:14 +0100
committerMasahiro Yamada <masahiroy@kernel.org>2020-12-21 05:57:08 +0100
commitbc72d723ec6b75c53e935e819682c3e67b83e9c1 (patch)
tree5f921ed293ba8c89cbc68ed3c8e1132c836ce882 /Documentation/networking/kcm.rst
parentkbuild: don't hardcode depmod path (diff)
downloadlinux-bc72d723ec6b75c53e935e819682c3e67b83e9c1.tar.xz
linux-bc72d723ec6b75c53e935e819682c3e67b83e9c1.zip
modpost: rename merror() to error()
The log function names, warn(), merror(), fatal() are inconsistent. Commit 2a11665945d5 ("kbuild: distinguish between errors and warnings in modpost") intentionally chose merror() to avoid the conflict with the library function error(). See man page of error(3). But, we are already causing the conflict with warn() because it is also a library function. See man page of warn(3). err() would be a problem for the same reason. The common technique to work around name conflicts is to use macros. For example: /* in a header */ #define error(fmt, ...) __error(fmt, ##__VA_ARGS__) #define warn(fmt, ...) __warn(fmt, ##__VA_ARGS__) /* function definition */ void __error(const char *fmt, ...) { <our implementation> } void __warn(const char *fmt, ...) { <our implementation> } In this way, we can implement our own warn() and error(), still we can include <error.h> and <err.h> with no problem. And, commit 93c95e526a4e ("modpost: rework and consolidate logging interface") already did that. Since the log functions are all macros, we can use error() without causing "conflicting types" errors. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'Documentation/networking/kcm.rst')
0 files changed, 0 insertions, 0 deletions