From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
linux-doc@vger.kernel.org,
Masahiro Yamada <mchehab+huawei@kernel.org>,
Nathan Chancellor <mchehab+huawei@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] docs: kernel-doc: doesn't suppress error/warnings
Date: Tue, 20 May 2025 07:47:44 +0200 [thread overview]
Message-ID: <cover.1747719873.git.mchehab+huawei@kernel.org> (raw)
As discussed at:
https://lore.kernel.org/all/20250516200350.63be46cd@canb.auug.org.au/
Sphinx logger is set in a way that errors/warnings from kernel-doc are
suppressed, except when V=1.
Finding the root cause is not trivial, as we need to go into the Sphinx
overlays on the top of Python's default logger class. Instead, let's take
the trivial approach: use logger class directly. As we can later revisit
such decision, let's add a comment at the code.
Mauro Carvalho Chehab (1):
docs: kerneldoc.py: don't use Sphinx logger
Documentation/sphinx/kerneldoc.py | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--
2.49.0
next reply other threads:[~2025-05-20 5:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 5:47 Mauro Carvalho Chehab [this message]
2025-05-20 5:47 ` [PATCH 1/1] docs: kerneldoc.py: don't use Sphinx logger Mauro Carvalho Chehab
2025-05-20 5:55 ` Randy Dunlap
2025-05-20 7:50 ` Mauro Carvalho Chehab
2025-05-20 8:23 ` Akira Yokosawa
2025-05-20 9:19 ` Mauro Carvalho Chehab
2025-05-20 11:39 ` Stephen Rothwell
2025-05-20 13:09 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1747719873.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.schier@linux.dev \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.