From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f198.google.com (mail-pf1-f198.google.com [209.85.210.198]) by kanga.kvack.org (Postfix) with ESMTP id D596B6B0266 for ; Tue, 2 Oct 2018 12:47:49 -0400 (EDT) Received: by mail-pf1-f198.google.com with SMTP id e15-v6so540027pfi.5 for ; Tue, 02 Oct 2018 09:47:49 -0700 (PDT) Received: from mga04.intel.com (mga04.intel.com. [192.55.52.120]) by mx.google.com with ESMTPS id w4-v6si10228207pll.214.2018.10.02.09.47.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Oct 2018 09:47:49 -0700 (PDT) Message-ID: <23e8d0a3b0e5649a74ec1fd8ef9975856fdc7eab.camel@intel.com> Subject: Re: [RFC PATCH v4 02/27] x86/fpu/xstate: Change some names to separate XSAVES system and user states From: Yu-cheng Yu Date: Tue, 02 Oct 2018 09:43:05 -0700 In-Reply-To: <6859a180-8973-e794-7ac4-1ac8f0e1c709@linux.intel.com> References: <20180921150351.20898-1-yu-cheng.yu@intel.com> <20180921150351.20898-3-yu-cheng.yu@intel.com> <20181002152903.GB29601@zn.tnic> <498c8824-9255-96be-71c2-3ebfa684a9d3@linux.intel.com> <20181002163736.GD29601@zn.tnic> <6859a180-8973-e794-7ac4-1ac8f0e1c709@linux.intel.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Dave Hansen , Borislav Petkov Cc: x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, Arnd Bergmann , Andy Lutomirski , Balbir Singh , Cyrill Gorcunov , Florian Weimer , "H.J. Lu" , Jann Horn , Jonathan Corbet , Kees Cook , Mike Kravetz , Nadav Amit , Oleg Nesterov , Pavel Machek , Peter Zijlstra , Randy Dunlap , "Ravi V. Shankar" , Vedvyas Shanbhogue On Tue, 2018-10-02 at 09:39 -0700, Dave Hansen wrote: > On 10/02/2018 09:37 AM, Borislav Petkov wrote: > > This patch's commit message is not even close. So I'd very much > > appreciate a more verbose explanation, even if it repeats itself at > > places. > > Yep, totally agree. Ok, I will work on that. Yu-cheng