linux-kernel - Re: [PATCH v6 04/15] x86/pvh: Use fixed_percpu

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: <85E9A42F-EB78-4F82-9099-B01A18CA16D2@alien8.de>
Date: Sun, 26 Jan 2025 04:57:22 +0100
From: Borislav Petkov <bp@...en8.de>
To: Brian Gerst <brgerst@...il.com>
CC: linux-kernel@...r.kernel.org, x86@...nel.org, Ingo Molnar <mingo@...nel.org>,
 "H . Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de>,
 Ard Biesheuvel <ardb@...nel.org>, Uros Bizjak <ubizjak@...il.com>,
 Juergen Gross <jgross@...e.com>, xen-devel@...ts.xenproject.org
Subject: Re: [PATCH v6 04/15] x86/pvh: Use fixed_percpu_data for early boot GSBASE

On January 25, 2025 5:51:29 PM GMT+01:00, Brian Gerst <brgerst@...il.com> wrote:
>To be fair, this was a copy of an existing comment.  Is there a style
>guide where all these grammar rules are documented, so I don't have to
>keep resending these patches for trivial typos?

You don't have to keep resending them for trivial typos - you simply wait 1-2 weeks to gather review feedback, you incorporate it and send a new version of the set. Like it is usually done on lkml. I think you know how the process works...

-- 
Sent from a small device: formatting sucks and brevity is inevitable.