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.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,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 E16DFC4CECE for ; Mon, 14 Oct 2019 21:18:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A45A720640 for ; Mon, 14 Oct 2019 21:18:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="J0FjW/tG" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732016AbfJNVSf (ORCPT ); Mon, 14 Oct 2019 17:18:35 -0400 Received: from mail.skyhub.de ([5.9.137.197]:55954 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731672AbfJNVSf (ORCPT ); Mon, 14 Oct 2019 17:18:35 -0400 Received: from zn.tnic (p200300EC2F065800329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2f06:5800:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 00BA01EC0C31; Mon, 14 Oct 2019 23:18:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1571087913; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=lJDIS6qAo6rnwlSCT9/pbXVO7qJtsNwnZrYxxlfr9S4=; b=J0FjW/tGdfErf5SSe4pHEpVZ0cPl22tHByaKRtdroYDaim+Z4f4i0OG2FVLwpvpp67Y+EC lJEkYbrpqpqTUNWnYf8JHpBpmOja0+SLZeMvrsxC/GcTY9lJKXVo8GxVPd1d6DID2SYbFf a1mIpKcPwyEZKUVsSzPSjRcWn7aIWw4= Date: Mon, 14 Oct 2019 23:18:25 +0200 From: Borislav Petkov To: Jarkko Sakkinen 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: <20191014211825.GJ4715@zn.tnic> References: <20191012034421.25027-1-kasong@redhat.com> <20191014101419.GA4715@zn.tnic> <20191014202111.GP15552@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20191014202111.GP15552@linux.intel.com> 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: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. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette