Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756741AbbLBILq (ORCPT ); Wed, 2 Dec 2015 03:11:46 -0500 Received: from mga01.intel.com ([192.55.52.88]:3483 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753901AbbLBILp (ORCPT ); Wed, 2 Dec 2015 03:11:45 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,372,1444719600"; d="scan'208";a="6016185" Date: Wed, 2 Dec 2015 10:11:14 +0200 From: Jarkko Sakkinen To: Jason Gunthorpe Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Martin Wilck , Peter Huewe , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Subject: Re: [PATCH v2 0/3] tpm_tis: Clean up force module parameter Message-ID: <20151202081114.GA3458@intel.com> References: <1448996309-15220-1-git-send-email-jgunthorpe@obsidianresearch.com> <20151201213351.GC5071@intel.com> <20151201222223.GA27480@obsidianresearch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151201222223.GA27480@obsidianresearch.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1554 Lines: 42 On Tue, Dec 01, 2015 at 03:22:23PM -0700, Jason Gunthorpe wrote: > 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? > > These changes are complex enough they really shouldn't go into 4.4 > unless absolutely necessary. The reasons I'm asking this are: * I'm planning to do v4.5 pull request soon. * If this need to be get this into v4.4, we should act fast. Given the complexity of the changes I'd not recommend that unless it is a life and death question. > > Could you possibly make these apply on top of security/next and > > re-submit if needed? > > It isn't trivial to reorder all 10 patches to do this, I'd like to > know we need to do this for sure first. Uwe? Agreed. First we have to know whether these changes have go to v4.4. > Jason /Jarkko -- 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/