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.2 required=3.0 tests=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 4D5E1C432C2 for ; Wed, 25 Sep 2019 14:32:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2F870222BD for ; Wed, 25 Sep 2019 14:32:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2437543AbfIYOcP (ORCPT ); Wed, 25 Sep 2019 10:32:15 -0400 Received: from mga05.intel.com ([192.55.52.43]:61657 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2437443AbfIYOcO (ORCPT ); Wed, 25 Sep 2019 10:32:14 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Sep 2019 07:32:12 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,548,1559545200"; d="scan'208";a="340424041" Received: from kmakows-mobl.ger.corp.intel.com (HELO localhost) ([10.249.39.225]) by orsmga004.jf.intel.com with ESMTP; 25 Sep 2019 07:32:05 -0700 Date: Wed, 25 Sep 2019 17:32:04 +0300 From: Jarkko Sakkinen To: Andy Lutomirski Cc: Dave Hansen , LKML , X86 ML , linux-sgx@vger.kernel.org, Andrew Morton , "Christopherson, Sean J" , nhorman@redhat.com, npmccallum@redhat.com, "Ayoun, Serge" , "Katz-zamir, Shay" , "Huang, Haitao" , Andy Shevchenko , Thomas Gleixner , "Svahn, Kai" , Borislav Petkov , Josh Triplett , "Huang, Kai" , David Rientjes , "Xing, Cedric" Subject: Re: [PATCH v22 00/24] Intel SGX foundations Message-ID: <20190925143204.GE19638@linux.intel.com> References: <20190903142655.21943-1-jarkko.sakkinen@linux.intel.com> <20190914134136.GG9560@linux.intel.com> <8339d3c0-8e80-9cd5-948e-47733f7c29b7@intel.com> <20190916052349.GA4556@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: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 24, 2019 at 10:20:09AM -0700, Andy Lutomirski wrote: > > I think either can be considered post-upstreaming. > > Indeed, as long as the overall API is actually compatible with these > types of restrictions. I include LSM changes to the follow up versions of the patch set. This is done to help verify that the API is compatible (or make it easy to review). I think they should be merged only after SGX is in the upstream beause this will make testing and reviewing smaller details of the changes less edgy the for LSM maintainers when one can just grab the LSM changes and try them out with the mainline. /Jarkko