Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp2989399pxm; Mon, 28 Feb 2022 09:50:29 -0800 (PST) X-Google-Smtp-Source: ABdhPJxOpcJppmicg77glrAuTh+OhVZnIskURLY9IJ3TlyvCyFwD0KohnMh6Bj7PSWYygftEkepG X-Received: by 2002:a05:6a00:1510:b0:4f0:ef18:4992 with SMTP id q16-20020a056a00151000b004f0ef184992mr22778731pfu.86.1646070628901; Mon, 28 Feb 2022 09:50:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646070628; cv=none; d=google.com; s=arc-20160816; b=hIxUq8GtGyCsfdYptJHfvBzS/TFN8bep0vCMLjgczlsOv86Y8EvIE5RxGboscaCbn7 gQ0q/G4gi/noAssopEG/oXSBHYntTNLh7CCjHtma9jD3aUhrEpWKu3FMcbYLme5WmeCn ZMzNgNk/N+CdBiWbng1ixUKMg/gyg0Jev5DR0mRqk7HMTzSE1Z+oUKSoUEbW6Yo6HYmQ +sTbSX4JflBOVGL0kKuvvekYaPaqea97IPflW6O50yi561vlZxwhmCfc7k2NCgjYSXcp uojKEYGJ1EmbrbpNySIi/QlVHiwfOrdtKtemcqBNkFkJQuuB69fT2r65xWFalwR1rzf9 nUlQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:subject :from:references:cc:to:content-language:user-agent:mime-version:date :message-id:dkim-signature; bh=2o2kBPkUMX//ZZfX33JRQfzuvoaqK1nEfvRcrffMfPU=; b=iPOFNrcYA1DzONoNOYpLcWOr3kUrSY9XkCxypxzJNk2Hg560bsd0pgsL0aagWw/Wbb ItHjU0MqjSTYyQUKXIpXntULcRU2+WDAIoubNYRIE47ccg7ymEu7fY341FCX5hzK3z4P 5wsJpEDEvlVQ3W+IiHkORCX3QvWVl5/nVczArTLqyixqK3HlLjJSaHKFHnm14zK+NgCR eaAZ9Nn0MTWVkpkgek8w/xyQTduO3eAlf5HQCBqG3ZGzOCY+KtUryE4kUidBx/cKQrsC h+HtnlbJO/m4iqUcH+uGPTyTrXBsK2rpj4LD8amDwp4Ct1FTLH0s2bi6djDmMQAG48Eg BgvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=fevIJdCg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q8-20020a17090311c800b0014faeb2d479si11023103plh.424.2022.02.28.09.50.13; Mon, 28 Feb 2022 09:50:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=fevIJdCg; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237818AbiB1QwK (ORCPT + 99 others); Mon, 28 Feb 2022 11:52:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58010 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237394AbiB1QwJ (ORCPT ); Mon, 28 Feb 2022 11:52:09 -0500 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4701685BE3 for ; Mon, 28 Feb 2022 08:51:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1646067090; x=1677603090; h=message-id:date:mime-version:to:cc:references:from: subject:in-reply-to:content-transfer-encoding; bh=JVHgOaqEAHLfUif8xihCvc1RrqNb4vLpIVTphrUcEHY=; b=fevIJdCg4+wQcCr7hR7wCnsisIvmgVvsNSmtCH96Z/Hbeg20LZQ9UI7X 37eek5HClG8bpYWS4kOtSByFDJirIMFU0u75bHyHDd9OgiFjjnnoP0G5R ow5aHlkBXbGQHRwNM+6RuuqWY98AWXb3E+qTyVJlzv9VEPYxQKOEyiQ/d rjhhf9sNLfJceQ0cvB0CtNFTDQ5Xph8k9wjL+CzB/SJDszmtjMyKVf1BU /0rsXhC1Z44licQxWC1BB+gkLkLjwotob7QYWIjl4tUy9es4G75WI4dqJ 31OfouL8lbYOfEcC+M54JyN2gaJZEZ7JH53QWEpynGJkkoDd5pwkJg+ad Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10272"; a="250511941" X-IronPort-AV: E=Sophos;i="5.90,142,1643702400"; d="scan'208";a="250511941" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Feb 2022 08:51:25 -0800 X-IronPort-AV: E=Sophos;i="5.90,142,1643702400"; d="scan'208";a="550314170" Received: from eliasbro-mobl.amr.corp.intel.com (HELO [10.212.174.65]) ([10.212.174.65]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Feb 2022 08:51:23 -0800 Message-ID: <080f9306-8c72-c7bd-010a-f0ed32c4b692@intel.com> Date: Mon, 28 Feb 2022 08:51:20 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US To: Josh Poimboeuf , "Kirill A. Shutemov" Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, luto@kernel.org, peterz@infradead.org, sathyanarayanan.kuppuswamy@linux.intel.com, aarcange@redhat.com, ak@linux.intel.com, dan.j.williams@intel.com, david@redhat.com, hpa@zytor.com, jgross@suse.com, jmattson@google.com, joro@8bytes.org, knsathya@kernel.org, pbonzini@redhat.com, sdeep@vmware.com, seanjc@google.com, tony.luck@intel.com, vkuznets@redhat.com, wanpengli@tencent.com, thomas.lendacky@amd.com, brijesh.singh@amd.com, x86@kernel.org, linux-kernel@vger.kernel.org, David Rientjes References: <20220224155630.52734-1-kirill.shutemov@linux.intel.com> <20220224155630.52734-2-kirill.shutemov@linux.intel.com> <20220227220130.23yjme7jucxo266l@treble> <20220228162056.gul22bjr4w6zjslq@black.fi.intel.com> <20220228164007.nfrg7xvrl4blzzrm@treble> From: Dave Hansen Subject: Re: [PATCHv4 01/30] x86/mm: Fix warning on build with X86_MEM_ENCRYPT=y In-Reply-To: <20220228164007.nfrg7xvrl4blzzrm@treble> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/28/22 08:40, Josh Poimboeuf wrote: >> maintainer-tip.rst seems disagree with you: >> >> A Fixes tag should be added even for changes which do not need to be >> backported to stable kernels, i.e. when addressing a recently introduced >> issue which only affects tip or the current head of mainline. >> >> I will leave it as is. > How does that disagree with me? > > The "Fixes" tag is for bug fixes. If it's not possible to trigger the > warning and there's no user impact, it's not a bug. Does having Fixes: *break* anything? If not, I think I'd generally rather have the metadata with more information as opposed to less information.