linux-kernel - Re: [PATCH printk v3 5/6] printk: introduce console_get_next_message() and console

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Y7Q2IYjMi3B+g7mU@alley>
Date:   Tue, 3 Jan 2023 15:05:21 +0100
From:   Petr Mladek <pmladek@...e.com>
To:     John Ogness <john.ogness@...utronix.de>
Cc:     Sergey Senozhatsky <senozhatsky@...omium.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH printk v3 5/6] printk: introduce
 console_get_next_message() and console_message

On Tue 2023-01-03 11:08:27, John Ogness wrote:
> On 2022-12-21, John Ogness <john.ogness@...utronix.de> wrote:
> > +/**
> > + * console_message - Container for a prepared console message.
> 
> This documentation is not included in the kerneldocs, but it should at
> least be proper kerneldoc format. It should be:
> 
>  * struct console_message - Container for a prepared console message.

Great catch!

Best Regards,
Petr