Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp2393594imm; Sat, 23 Jun 2018 17:29:56 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJLGmqk2ARtuYTLoVInyBmLZQTr+mvb0EU2yVRzfqytWIgH9PlZWE82mAPsGDBdn7Z54/RI X-Received: by 2002:a65:4a04:: with SMTP id s4-v6mr6026023pgq.376.1529800196047; Sat, 23 Jun 2018 17:29:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529800196; cv=none; d=google.com; s=arc-20160816; b=GjfsIK+PHiAekgXebSYpU15wYMddp5yiIsYIm3A6jGqPAliv2jg/dcycZ7Bt+7I4wj DmjmBHd+acTRh7BfKCQiF0ClDhtSMSTKqh8Rubm2K+R1GGP63bLpkA34wTTuw4xe0gWX poSmIFkyz03ybTPtWfKrZyPjuUZuJk8PclKhyAh5swWuUWBZgXpA5RpnKvuXfMh77vQd 9TxW9qG6fKz20qO0sgIak4xVzFkUknAiTt/7t8TEJS7wXaSc1artzTDllq6PxVcM8Nqy iV+/H/4wbon+URAoEadf2YpXzUHl00bS0pvWkc2jSquIl1oOK708JnK+rfeIgJuEP8YI Ddrg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=fq0DtP5WhTsl8NG30zUEr5GTcMVlYuZVmm+c4eDGS94=; b=sClVIbO4NOMqOu+l1Ck/flb+1wdrbnp4saeZE0kLy6kxv7ll75hPcH/Xa/q93Xhbqy 9yxQCbw04IQRgrrk0laJn4fTXBjTZshBxRt2oU1tYjHuijkN1wNsFdCMCiFfw119dlBC azyraGEaeMxF2J6uGUGW/0RM8zcqhSAriR+pstaCwYfGkQ78MPVQ986X8eF3Xe6wLZ0k YafQwyJ5xnM029EKuI0PVtGWrcLB1Jxbg5H03EI/vVn6txOn2yEmvExApdbulVSQRYHa MAnpIK0h4WsL4jZ4i5PmokOB1+z4WLrAMLBxFm8vnxmpoO9nYJ6FFuxltWEkDp7smXK0 Mgbg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j84-v6si10589806pfj.79.2018.06.23.17.29.39; Sat, 23 Jun 2018 17:29:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751949AbeFXA27 (ORCPT + 99 others); Sat, 23 Jun 2018 20:28:59 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:44099 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751690AbeFXA26 (ORCPT ); Sat, 23 Jun 2018 20:28:58 -0400 Received: from p4fea482e.dip0.t-ipconnect.de ([79.234.72.46] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fWste-0000VS-Ba; Sun, 24 Jun 2018 02:28:50 +0200 Date: Sun, 24 Jun 2018 02:28:49 +0200 (CEST) From: Thomas Gleixner To: David Howells cc: Reinette Chatre , fenghua.yu@intel.com, Tony Luck , vikas.shivappa@linux.intel.com, gavin.hindman@intel.com, jithu.joseph@intel.com, dave.hansen@intel.com, mingo@redhat.com, "H. Peter Anvin" , x86@kernel.org, LKML , Al Viro Subject: Re: [PATCH V7 00/41] Intel(R) Resource Director Technology Cache Pseudo-Locking enabling In-Reply-To: <15108.1529795694@warthog.procyon.org.uk> Message-ID: References: <15108.1529795694@warthog.procyon.org.uk> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 24 Jun 2018, David Howells wrote: > Thomas Gleixner wrote: > > > - Stick the struct into the local header file and not at some random place in > > the source. > > Why? It's only used in that one file. There doesn't seem to be any > particular need to share it around. It's not in a global header. It's a local header exactly to stick stuff like that into it. > > - Get rid of the fugly camel case > > It's not camel case. It's the name of the option it's encoding. But if it > makes you happy... Well, the option name slipped through, but that doesn't make an excuse for making the struct member equally ugly. Thanks, tglx