linux-kernel - Re: [PATCH v12 02/12] printk: Make vprintk

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: <20250709150452.6646c168@batman.local.home>
Date: Wed, 9 Jul 2025 15:04:52 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Nam Cao <namcao@...utronix.de>
Cc: John Ogness <john.ogness@...utronix.de>, Masami Hiramatsu
 <mhiramat@...nel.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
 Gabriele Monaco <gmonaco@...hat.com>, linux-trace-kernel@...r.kernel.org,
 linux-kernel@...r.kernel.org, Petr Mladek <pmladek@...e.com>, Sergey
 Senozhatsky <senozhatsky@...omium.org>
Subject: Re: [PATCH v12 02/12] printk: Make vprintk_deferred() public

On Wed, 9 Jul 2025 20:53:34 +0200
Nam Cao <namcao@...utronix.de> wrote:

> It is possible that you make this amendment when/if you apply the patch, or
> do you prefer me sending a new version?

I could do it, but if you send a new version, it will keep patchwork
automated. When I edit a patch, the status doesn't automatically get
updated due to the change.

I know it's minor, but could you send a v13? Then when the patch gets
accepted in mainline, it should automatically turn to Accept in
patchwork.

Thanks,

-- Steve