Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757568AbbLBJKl (ORCPT ); Wed, 2 Dec 2015 04:10:41 -0500 Received: from mout.gmx.net ([212.227.15.18]:59105 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755191AbbLBJKi convert rfc822-to-8bit (ORCPT ); Wed, 2 Dec 2015 04:10:38 -0500 User-Agent: K-9 Mail for Android In-Reply-To: <20151202081423.GB3458@intel.com> References: <1448996309-15220-1-git-send-email-jgunthorpe@obsidianresearch.com> <20151201213351.GC5071@intel.com> <20151201222223.GA27480@obsidianresearch.com> <7BE9D077-675D-42FE-9461-81317CCA3762@gmx.de> <20151202081423.GB3458@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Subject: Re: [PATCH v2 0/3] tpm_tis: Clean up force module parameter From: Peter Huewe Date: Wed, 02 Dec 2015 01:02:13 -0800 To: Jarkko Sakkinen CC: Jason Gunthorpe , tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Martin Wilck , =?ISO-8859-1?Q?Uwe_Kleine-K=F6nig?= Message-ID: <1EB6498E-9E04-449A-8913-0BDFB27BA04D@gmx.de> X-Provags-ID: V03:K0:1WaeIIiGeG4cc6kKEwW8H8MqMfhQF/fPI0YnvJUPl1hr1z1yWJJ US9gEhvfLUagKjs5oeourogbPzJjjGPGeCm/dl5cJpVb8jc+HKfEvalTFOoQ2TuYqfF5FZd H+++dcKJH3Wt/o6mG/lvuHbe5opKkzC5u1EPKodFkPm9kiG9eaKYiPABtoyaf/PL2Xx5OZT +CA91DRMe3CibvxwV6ePg== X-UI-Out-Filterresults: notjunk:1;V01:K0:eUX9pL5lFaQ=:nhkzKmwhwgSn1mo1Uws8f1 Q0BQRVQzjRNE0Q2xH3AHZKkw6ynxhO95IO45gIgcTUOCkmZLIGyHWdiJoLPxpiH7yrRJXKl9t mylTFpR481hPmPUaXiUaVzOcCJ8/RgxWidyUj+s9kpkNiqPvq18lp1LQvAxKahWJMF5ZFtGOd fYC7T2m3QJ4RI42yz7BiajnI52NiVv1EBSMJin9YzSdD4cfNP+Q2qLMO8Yw8GbHZUMEPsUcZA Dit5laayhBL+COW9XwrGqiQuACJZR3G0kHVvfHRekvnpPh35ekHvb1gYcuQD3SjciESjqfEn1 os6AFYFPt9TsXYcXZElS/OrO3B6lptwMD0Osi06xlUGmzuLwIVXjdK+vGiUjqATjws3vNOYqK vE9JXRwF/uIVVjqLri6KYzSEtpTMkhc0DDKnlUmRqfPT4C9YDMikKsQRUsLj3kgNyzwVs+4CB ZRN5PY9LlnTAY/+enVEickQQVbs+u29hiz5AXsMbP4EAJjTeED0rs9Skz7Z+yHUrf0y5mDF0C nhc1AIKIrmXfoqSRKbd7laMXipMylYV2Fwxli3keAekaTID4CGOa/W02UbriyzV06zQlqPj91 7tXm+6sW1wXMXkNSk0XH35zpsmXZ5XHpPihkTogjzVN+AhsR8wzn78gjm8ovxCkTZHKoLHRuD JITm5Utt3t6dbTbTxQi7Xa/YloRsNFvDPlOTRp2e7JFhEHIC6m/VcfjzO8GepwKX0rPVushcG 4rrBio/UemMYFd3JIBPPlVJaWuK1f2snz/XFX3B2CXEWrt9WsbAhCpoHLgxzmmrjSIAxXPL1I KYbPDQl Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1566 Lines: 50 Am 2. Dezember 2015 00:14:23 PST, schrieb Jarkko Sakkinen : >On Tue, Dec 01, 2015 at 05:15:14PM -0800, Peter Huewe wrote: >> >> >> Am 1. Dezember 2015 14:22:23 PST, schrieb Jason Gunthorpe >: >> >On Tue, Dec 01, 2015 at 11:33:51PM +0200, Jarkko Sakkinen wrote: >> > >> >> I went through the patches and didn't see anything that would >shock >> >me >> >> enough not to apply the patches in the current if they also work >when >> >> tested *but* are these release critical for Linux v4.4? >> >> >> >> I got a bit confused about the discussion that was going on about >> >"where >> >> to fix the probe" crash whether or not both it should be fixed in >> >both >> >> places. >> > >> >I'm also confused by that.. >> > >> >It sounds like force=1 is broken in 4.4 right now - do we care? >Should >> >we fix this by using Martin's patch? >> >> I'm not 100% sure if force=1 is broken in 4.3 as well, as I oops when >> I have my tpm_crb loaded and then call modprobe tpm_tis force=1 >> Peter > >It'd have to be a different regression because v4.3 does not contain >the >change that breaks this in v4.4. You had a NUC with discrete TPM >module, >am I remembering right? > Nope, intel fw tpm2.0 in my acer laptop. No nucs here >/Jarkko -- Sent from my mobile -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/