From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Christian Bundy <christianbundy@fraction.io>,
Jason Gunthorpe <jgg@ziepe.ca>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Peter Huewe <peterhuewe@gmx.de>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
stable-commits@vger.kernel.org, linux-integrity@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Patch "tpm_tis: reserve chip for duration of tpm_tis_core_init" has been added to the 5.4-stable tree
Date: Sat, 28 Dec 2019 17:15:26 +0200 [thread overview]
Message-ID: <20191228151526.GA6971@linux.intel.com> (raw)
In-Reply-To: <50217a688ffa56cf5f150ffd358daba2a88cad48.camel@linux.intel.com>
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?
[*] https://patchwork.kernel.org/project/linux-integrity/list/?series=208305
/Jarkko
next prev parent reply other threads:[~2019-12-28 15:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1577122577157232@kroah.com>
2019-12-23 19:46 ` Patch "tpm_tis: reserve chip for duration of tpm_tis_core_init" has been added to the 5.4-stable tree Dan Williams
2019-12-27 6:05 ` Jarkko Sakkinen
2019-12-27 6:11 ` Jarkko Sakkinen
2019-12-28 15:15 ` Jarkko Sakkinen [this message]
2019-12-28 17:17 ` Dan Williams
2019-12-30 7:41 ` Dan Williams
2019-12-30 23:28 ` Jarkko Sakkinen
2019-12-31 0:33 ` Jerry Snitselaar
2019-12-31 1:02 ` Jerry Snitselaar
2019-12-31 16:00 ` Jarkko Sakkinen
2019-12-31 19:47 ` Christian Bundy
2020-01-02 17:20 ` Jarkko Sakkinen
2020-01-02 19:20 ` Dan Williams
2020-01-03 5:04 ` Dan Williams
2020-01-03 22:20 ` Jerry Snitselaar
2020-01-03 22:55 ` Jarkko Sakkinen
2020-01-03 21:51 ` Jarkko Sakkinen
2020-01-03 20:24 ` Jerry Snitselaar
2020-01-03 22:56 ` Jarkko Sakkinen
2020-01-03 23:07 ` Jarkko Sakkinen
2020-01-03 23:30 ` Jarkko Sakkinen
2020-01-03 21:47 ` Jerry Snitselaar
2019-12-31 0:30 ` Jerry Snitselaar
2020-01-01 22:55 ` Dan Williams
2019-12-28 23:39 ` Jerry Snitselaar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191228151526.GA6971@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=christianbundy@fraction.io \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stable-commits@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.