From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Christian Bundy <christianbundy@fraction.io>,
Dan Williams <dan.j.williams@intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>, 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, 04 Jan 2020 01:07:08 +0200 [thread overview]
Message-ID: <2f4850d8ab10fbe421deff11e8c3b18bfeaace65.camel@linux.intel.com> (raw)
In-Reply-To: <20200103202458.lhd5qu2onl67kilb@cantor>
On Fri, 2020-01-03 at 13:24 -0700, Jerry Snitselaar wrote:
> On Thu Jan 02 20, Jarkko Sakkinen wrote:
> > On Tue, Dec 31, 2019 at 11:47:37AM -0800, Christian Bundy wrote:
> > > > Christian, were you having any issues with interrupts? You system was going
> > > > into this code as well.
> > >
> > > Unfortunately I'm now unable to test, sorry for the trouble. I replaced my BIOS
> > > with UEFI firmware and the problem has disappeared. Please let me know if there
> > > is anything else I can do to help.
> > >
> > > Christian
> >
> > Takashi wrote yesterday [*]:
> >
> > "I'm building a test kernel package based on 5.5-rc4 with Jarkko's revert
> > patches"
> >
> > [*] https://bugzilla.kernel.org/show_bug.cgi?id=205935
> >
> > /Jarkko
> >
>
> You can add my ack to the reverts.
I'll actually send a patch set to linux-integrity (ETA 1-2h) and
you can tag it then.
Better to have sanity check before I send the PR so please check the
patches and give your feedback ASAP. Please also the check that the
commit messages look good and also that the cover letter as I'll use
that as basis for my pull request message.
/Jarkko
next prev parent reply other threads:[~2020-01-03 23:07 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
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 [this message]
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=2f4850d8ab10fbe421deff11e8c3b18bfeaace65.camel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox