[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191016154842.GJ1138@zn.tnic>
Date: Wed, 16 Oct 2019 17:48:42 +0200
From: Borislav Petkov <bp@...en8.de>
To: Joe Perches <joe@...ches.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Kairui Song <kasong@...hat.com>, linux-kernel@...r.kernel.org,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Matthew Garrett <matthewgarrett@...gle.com>,
Baoquan He <bhe@...hat.com>, Dave Young <dyoung@...hat.com>,
x86@...nel.org, linux-efi@...r.kernel.org,
linux-integrity@...r.kernel.org
Subject: Re: [PATCH v3] x86, efi: never relocate kernel below lowest
acceptable address
On Wed, Oct 16, 2019 at 08:23:56AM -0700, Joe Perches wrote:
> ? examples please.
>From this very thread:
\sEfi\s, \sefi\s, \seFI\s etc should be "EFI"
I'm thinking perhaps start conservatively and catch the most often
misspelled ones in commit messages or comments. "CPU", "SMT", "MCE",
"MCA", "PCI" etc come to mind.
> checkpatch has a db for misspellings, I supposed another for
> acronyms could be added,
Doesn't have to be another one - established acronyms are part of the
dictionary too.
> but how would false positives be avoided?
Perhaps delimited with spaces or non-word chars (\W) and when they're
part of a comment or the commit message...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists