[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aCyPFAKhSQIFR_lJ@smile.fi.intel.com>
Date: Tue, 20 May 2025 17:17:56 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Jonathan Corbet <corbet@....net>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Nicolas Schier <nicolas.schier@...ux.dev>,
Akira Yokosawa <akiyks@...il.com>,
Randy Dunlap <rdunlap@...radead.org>, linux-doc@...r.kernel.org,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] Some kernel-doc fixes
On Tue, May 20, 2025 at 03:33:05PM +0200, Mauro Carvalho Chehab wrote:
> Hi Jon,
>
> Let me consolidate some patches on a single PR to make life simpler
> for you. Those should address Stephen and Akira's concerns with
> regards to KernelDoc class usage via sphinx kerneldoc.py extension.
>
> Patch 1: don't let Sphinx suppress errors/warnings;
> Patch 2: fix a KeyError when trying to acess data from non-existing files;
> Patch 3: add try/except blocks to avoid crashes when handling bad
> kernel-doc markups;
> Patch 4: makes Lore and kernel-doc ML receive patches related
> to kernel-doc.py and get_abi.py.
>
> Patches 1 to 3 were already submitted on separate series. Patch 4 is new.
Can we actually utilise CONFIG_WERROR to fail the build. If yes, the build will
be failed. This is in align with the warnings in the C code.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists