From 618952f07e98be63ad4546ab5aa90d600cafdfc8 Mon Sep 17 00:00:00 2001 From: Yu Watanabe Date: Mon, 16 Feb 2026 14:35:19 +0900 Subject: [PATCH] CODING_STYLE: fix typo Follow-up for 83b4a5bb3d6a0f565aebcba975efad8dac73abea. --- docs/CODING_STYLE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/CODING_STYLE.md b/docs/CODING_STYLE.md index e15e6ee15e7..767ab6734bb 100644 --- a/docs/CODING_STYLE.md +++ b/docs/CODING_STYLE.md @@ -705,7 +705,7 @@ SPDX-License-Identifier: LGPL-2.1-or-later - Think about the log level you choose: for functions that are of the "logging" kind (see above), please ensure that failures we propagate should be logged about at `LOG_ERR` level. Failures that are noteworthy, but we proceed anyway, - should be loged at `LOG_WARN` level. Important informational messages should + should be logged at `LOG_WARN` level. Important informational messages should use `LOG_NOTICE` and regular informational messages should use `LOG_INFO`. Note that the latter is the default maximum log level, i.e. only `LOG_DEBUG` messages are hidden by default. -- 2.47.3