From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751397AbdFEHS6 (ORCPT ); Mon, 5 Jun 2017 03:18:58 -0400 Received: from mga01.intel.com ([192.55.52.88]:19437 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751297AbdFEHS5 (ORCPT ); Mon, 5 Jun 2017 03:18:57 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,299,1493708400"; d="scan'208";a="1178338699" Date: Mon, 5 Jun 2017 10:18:38 +0300 From: Mika Westerberg To: Greg Kroah-Hartman , Andreas Noever Cc: Michael Jamet , Yehezkel Bernat , Lukas Wunner , Amir Levy , Andy Lutomirski , Mario.Limonciello@dell.com, Jared.Dominguez@dell.com, Andy Shevchenko , linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 00/27] Thunderbolt security levels and NVM firmware upgrade Message-ID: <20170605071838.GJ3454@lahna.fi.intel.com> References: <20170602140524.23367-1-mika.westerberg@linux.intel.com> <20170603091704.GC1103@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170603091704.GC1103@kroah.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jun 03, 2017 at 06:17:04PM +0900, Greg Kroah-Hartman wrote: > On Fri, Jun 02, 2017 at 05:04:57PM +0300, Mika Westerberg wrote: > > Hi, > > > > This is a third version of the patch series adding support for Thunderbolt > > security levels and NVM firmware upgrade. PCs running Intel Falcon Ridge or > > newer need these in order to connect devices if the security level is set > > to "user(SL1) or secure(SL2)" from BIOS. > > All looks good to me, very nice work. Thanks! > I don't know what tree it should go in through, but if Andreas wants me > to take it, I will if I can get his signed-off-by. That would be perfect. Andreas, do you have any objections? I will prepare another version where I've fixed the VSEC vs. VSE thing in the capability rework patch.