From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A68C4FA372B for ; Wed, 16 Oct 2019 15:20:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 803362168B for ; Wed, 16 Oct 2019 15:20:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731530AbfJPPUX (ORCPT ); Wed, 16 Oct 2019 11:20:23 -0400 Received: from mga07.intel.com ([134.134.136.100]:7188 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387700AbfJPPUV (ORCPT ); Wed, 16 Oct 2019 11:20:21 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Oct 2019 08:20:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.67,304,1566889200"; d="scan'208";a="370829200" Received: from hagarwal-mobl1.gar.corp.intel.com (HELO localhost) ([10.252.5.165]) by orsmga005.jf.intel.com with ESMTP; 16 Oct 2019 08:20:15 -0700 Date: Wed, 16 Oct 2019 18:20:14 +0300 From: Jarkko Sakkinen To: Borislav Petkov Cc: Kairui Song , linux-kernel@vger.kernel.org, Ard Biesheuvel , Thomas Gleixner , Ingo Molnar , Matthew Garrett , Baoquan He , Dave Young , 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 Message-ID: <20191016152014.GC4261@linux.intel.com> References: <20191012034421.25027-1-kasong@redhat.com> <20191014101419.GA4715@zn.tnic> <20191014202111.GP15552@linux.intel.com> <20191014211825.GJ4715@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191014211825.GJ4715@zn.tnic> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-integrity-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-integrity@vger.kernel.org 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. /Jarkko