linux-kernel - Re: [PATCH printk v5 06/30] printk: nbcon: Add callbacks to synchronize with driver

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]

Date: Fri, 17 May 2024 16:40:18 +0200
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,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH printk v5 06/30] printk: nbcon: Add callbacks to
 synchronize with driver

On Fri 2024-05-17 16:06:30, John Ogness wrote:
> On 2024-05-17, Petr Mladek <pmladek@...e.com> wrote:
> > BTW: I wonder if you use AI for generating the commit message.
> >      My experience is that AI produces longer fancy sentences
> >      which might be good for a novel but they sometimes hide
> >      the important details.
> 
> I do not know if that is a compliment or an insult.
> 
> For the record, I do not use AI. The "long fancy sentences hiding
> important details" are coming from a sober brain... mine.

Ah, take it as a complaint then ;-) Complicated things are just hard
to explain.

> > My attempt of a more strightforwward explanation:
> 
> [...]
> 
> Your version does not mention why the generic code now needs to use the
> driver-specific locking, but I suppose that does not matter (and only
> adds confusion instead of explanation).

I removed these details on purpose. I think that they will be
easier to understand with the code.

Best Regards,
Petr