From: Joe Perches <joe@perches.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Borislav Petkov <bp@alien8.de>
Cc: Kairui Song <kasong@redhat.com>,
linux-kernel@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Matthew Garrett <matthewgarrett@google.com>,
Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
x86@kernel.org, linux-efi@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v3] x86, efi: never relocate kernel below lowest acceptable address
Date: Wed, 16 Oct 2019 08:23:56 -0700 [thread overview]
Message-ID: <fb0e7c13da405970d5cbd59c10005daaf970b8da.camel@perches.com> (raw)
In-Reply-To: <20191016152014.GC4261@linux.intel.com>
On Wed, 2019-10-16 at 18:20 +0300, Jarkko Sakkinen wrote:
> On Mon, Oct 14, 2019 at 11:18:25PM +0200, Borislav Petkov wrote:
> > On Mon, Oct 14, 2019 at 11:21:11PM +0300, Jarkko Sakkinen wrote:
> > > Was there a section in the patch submission documentation to point out
> > > when people send patches with all the possible twists for an acronym?
> >
> > I don't think so.
> >
> > > This is giving me constantly gray hairs with TPM patches.
> >
> > Well, I'm slowly getting tired of repeating the same crap over and over
> > again about how important it is to document one's changes and to write
> > good commit messages. The most repeated answers I'm simply putting into
> > canned reply templates because, well, saying it once or twice is not
> > enough anymore. :-\
> >
> > And yeah, I see your pain. Same here, actually.
> >
> > In the acronym case, I'd probably add a regex to my patch massaging
> > script and convert those typos automatically and be done with it.
>
> Wonder if checkpatch.pl could be extended to know acronyms e.g. have a
> db of known acronyms.
? examples please.
checkpatch has a db for misspellings, I supposed another for
acronyms could be added, but how would false positives be avoided?
next prev parent reply other threads:[~2019-10-16 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 3:44 [PATCH v3] x86, efi: never relocate kernel below lowest acceptable address Kairui Song
2019-10-14 10:14 ` Borislav Petkov
2019-10-14 20:21 ` Jarkko Sakkinen
2019-10-14 21:18 ` Borislav Petkov
2019-10-16 15:20 ` Jarkko Sakkinen
2019-10-16 15:23 ` Joe Perches [this message]
2019-10-16 15:48 ` Borislav Petkov
2019-10-16 23:25 ` Joe Perches
2019-10-16 16:27 ` Jarkko Sakkinen
2019-10-16 17:54 ` Joe Perches
2019-10-15 5:23 ` Kairui Song
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb0e7c13da405970d5cbd59c10005daaf970b8da.camel@perches.com \
--to=joe@perches.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=kasong@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).