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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 285F9C2D0CE for ; Sat, 28 Dec 2019 17:18:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EF881208C4 for ; Sat, 28 Dec 2019 17:18:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=intel-com.20150623.gappssmtp.com header.i=@intel-com.20150623.gappssmtp.com header.b="CBluK9BN" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726371AbfL1RSB (ORCPT ); Sat, 28 Dec 2019 12:18:01 -0500 Received: from mail-oi1-f178.google.com ([209.85.167.178]:45764 "EHLO mail-oi1-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726248AbfL1RSB (ORCPT ); Sat, 28 Dec 2019 12:18:01 -0500 Received: by mail-oi1-f178.google.com with SMTP id n16so6226537oie.12 for ; Sat, 28 Dec 2019 09:18:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QQb9gUF/kF+QGb1YAnMfnG5z8D5xbT49s3EVMzZZtcQ=; b=CBluK9BNCD3CqbBclvb/CqjTAW4mELSnQyoy5xbZXd7rECwk3SR5yi3Xx7KdDds6+d fvY2wO8bgcyzpRBmFwkZ6q+I6KAAkyqHkOTyuKwVt7q7vJ2JK4cWHpanbTczwri80ixU 62bfaJx02L7wKPfMhxI0HTONuQ7bV1gzEXu2JJrGi3EbKe5c/ycKzuPlBALQk0XRi1Zs NaI2pYc91y9VVwB1/CjnMPkjRXVCEqhLd+4plTUB9VlvJb3/WKJctko7p/giM/Ydne9L UpRiwsHjX6Z/YMsljlr3tGCZMzBxU1t8aZ7362X6wMlAyBFp7AVgeOjcITvDnEzs7AFw WH3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QQb9gUF/kF+QGb1YAnMfnG5z8D5xbT49s3EVMzZZtcQ=; b=nCPuvkAOxTWN5nl0hM4QIDj1UpX9Fr4y7I1Y7sy2HUsgxwbzESw8jkn3wW4N22krfr ANXwFFa7yZPPhpugq7HbzQ0N7rAonYxxnwDIGyFmQM8f/Dd+8DJZBDhixPkiDNI1Ovch yXDfVKGuP2pvzfwk8zMhBvUkh5ayxxDgALphVP9uZmIqu7OGmpKvxdJyQ+DwR8SqITxr MyKctZVVOlqwZdv5skCraExE8rsJcjJt2spHExuUq4xjlC7mpRLI9K/C4NXpiAHSuVXF KodYVBl8IXogiXsY/Q0wBpcCB3oVzzDf5/SLNFr5XZK2YrBo2CjoXHfvFj7CbaGk3A0x rC3w== X-Gm-Message-State: APjAAAXmYkUJcuiAJDE4D2J/347XpULFYSnifXobRBRXHmJyG8XOirYg aOw3AjZ5ld0LbA5bZ/Qyd81fbACh6+B8ufX4l46HSA== X-Google-Smtp-Source: APXvYqwemknthHi9yLx4JjT2to533i4B7dw54JsE7re71KV1fc7wz7TN5ETZiNlMa5c9q5VrlhdoVim8dRMHj3A9/dQ= X-Received: by 2002:aca:4c9:: with SMTP id 192mr4907748oie.105.1577553480633; Sat, 28 Dec 2019 09:18:00 -0800 (PST) MIME-Version: 1.0 References: <1577122577157232@kroah.com> <50217a688ffa56cf5f150ffd358daba2a88cad48.camel@linux.intel.com> <20191228151526.GA6971@linux.intel.com> In-Reply-To: <20191228151526.GA6971@linux.intel.com> From: Dan Williams Date: Sat, 28 Dec 2019 09:17:49 -0800 Message-ID: Subject: Re: Patch "tpm_tis: reserve chip for duration of tpm_tis_core_init" has been added to the 5.4-stable tree To: Jarkko Sakkinen Cc: Greg KH , Christian Bundy , Jason Gunthorpe , Jerry Snitselaar , Peter Huewe , Stefan Berger , stable-commits@vger.kernel.org, linux-integrity@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Dec 28, 2019 at 7:15 AM Jarkko Sakkinen wrote: > > On Fri, Dec 27, 2019 at 08:11:50AM +0200, Jarkko Sakkinen wrote: > > Dan, please also test the branch and tell if other patches are needed. > > I'm a bit blind with this as I don't have direct access to the faulting > > hardware. Thanks. [*] > > > > [*] https://lkml.org/lkml/2019/12/27/12 > > Given that: > > 1. I cannot reproduce the bug locally. > 2. Neither of the patches have any appropriate tags (tested-by and > reviewed-by). [*] > > I'm sorry but how am I expected to include these patches? Thanks for the branch, I'll get it tested on the failing hardware. Might be a few days due to holiday lag.