From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751526AbdKTWUe (ORCPT ); Mon, 20 Nov 2017 17:20:34 -0500 Received: from mga07.intel.com ([134.134.136.100]:30879 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751146AbdKTWUc (ORCPT ); Mon, 20 Nov 2017 17:20:32 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,430,1505804400"; d="scan'208";a="151585864" Date: Tue, 21 Nov 2017 00:20:28 +0200 From: Jarkko Sakkinen To: Thomas Gleixner Cc: intel-sgx-kernel-dev@lists.01.org, platform-driver-x86@vger.kernel.org, LKML , x86@kernel.org, Peter Zijlstra , Andy Lutomirski , Borislav Petkov Subject: Re: [PATCH v5 00/11] Intel SGX Driver Message-ID: <20171120222028.tugaad4bsj7vbm7i@linux.intel.com> References: <20171113194528.28557-1-jarkko.sakkinen@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 15, 2017 at 11:35:42AM +0100, Thomas Gleixner wrote: > On Mon, 13 Nov 2017, Jarkko Sakkinen wrote: > > Any reason why you did not CC the x86 maintainers and other x86 developers > who have had opinions on the first attempt to get SGX into the kernel? > > This is not some driver for a random peripheral. This has substantional > effects. I'm assuming you simply forgot or were not aware, but this is not > the way this works. > > Thanks, > > tglx I'll CC v6 to x86 maintainers. I'm sorry about this. /Jarkko