linux-kernel - Re: [PATCH 5/9] docs: kdoc: remove the KernelEntry::is_kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87y0u3d6tw.fsf@trenco.lwn.net>
Date: Sat, 07 Jun 2025 07:22:51 -0600
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/9] docs: kdoc: remove the
 KernelEntry::is_kernel_comment member

Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:

> Em Fri,  6 Jun 2025 10:34:34 -0600
> Jonathan Corbet <corbet@....net> escreveu:
>
>> entry::is_kernel_comment never had anything to do with the entry itself; it
>> is a bit of local state in one branch of process_name().  It can, in fact,
>> be removed entirely; rework the code slightly so that it is no longer
>> needed.
>> 
>> No change in the rendered output.
>> 
>> Signed-off-by: Jonathan Corbet <corbet@....net>
>
> Not sure about this one. The idea of those warnings are to detect 
> non-kerneldoc markups that typically comes when someone "imports"
> OOT drivers or Windows one into Linux.
>
> I remember I catched several such cases in the past with the help
> of those warnings.

I haven't removed the warning, just the use of that specific variable to
trigger it.

Thanks,

jon